Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  •  Officially announce the start of User Acceptance Tests (UAT)
  •  Check that the release instance uses the latest modules
  •  Add user account on the QA server
  •  Do User-Acceptance-Testing (UAT)

RC Phase

  •  Ensure deployability with Docker (Quickstart installation guide / Docker compose)
  •  Check that the release instance use the latest modules
  •  Start collecting the documentation from developers

GA Phase

  •  Merge release branches with main
  •  Create release in GitHub, versioned according to Version management and containing complete release notes (should publish automatically the release on PyPi and NPM)
  •  Update the openimis.json in assemblies main branch to use only official version (not RC)
  •  Update demo server (mark maintenance window on Demo: openIMIS)
  •  Demo: openIMIS Instance and Wiki page are up to date
  •  Mark all tickets in release as “Done” or push to the next release
  •  Check that Installation Guide supports installation of the latest release
  •  Check and update wiki page on Release 2024-1004
    •  All links on the release page and release sources page are working and are helpful; Dates are correct and the status is “GA”
    •  Analyze linked issues as an anonymous user
    •  “Highlights” of the release are written and coherent
  •  Check and update Sources Release 20232024-1004
    •  All source components link to the correct repository on GitHub, have the correct version, valid release notes and are reasonably named to similar repositories / package manager
  •  Formulate release notes in current release (Releases) and forward it to co-ordination desk for promotion (e.g. newsletter, Twitter)
  •  Check and update the Wikipedia page, that it refers to the latest release (number) and reflects the technical facts of openIMIS correctly

...

Start preparing the next release immediately after the current release.

...