Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Checklist

Release planning

  • Define the name of the release
  • Define the release date
  • Do retro-planning
    • RC: “release date” - 2 weeks
    • Alpha : “release date” - 6 weeks
    • Beta: “release date”- 8 weeks,
    • Development freeze : “release date” - 10 weeks
  • create the release on the QA server

Freeze Phase

  • Inform developer of the freeze
  • Create the release branches
  • Define the version of the modules based on semantic versioning
  • Check the Continuous Integration in details
  • Publish the release branch on PyPi and NPM (required to check the packaging)
  • Inform the integrator about the UAT timeline (Beta version)
    • add user account on the QA server

Alpha Phase

  • create release instance using the released modules
  • perform some basic testing
    • Claim: create/review/process
    • Registration: create/update familly/insuree
    • Enrollment: create policy and contribution
    • Meta data: create/update location/product/user/role/pricelist/itemslist/servicelist
  • Make sure defects are assigned to developpers

Beta Phase

  • Update the PyPi, NPM module when code change was done
  • Check that the release instance use the latest modules
  •  

RC Phase

  • Update the PyPi, NPM module when code change was done
  • Check that the release instance use the latest modules
  • Start collecting the documentation from developers

GA Phase

  • Update the openimis.json to use only official version (not rc) on assembly modules
  • Merge release branches with main
  • make sure the demo server is up to date

Post-Release (prepare next release)

Preparation and Deployment

Releases Page Releases

  • Analyze linked issues as a normal user (private projects hidden)
  • All links are working and are helpful
  • Dates and status of all releases are correct

Release Page

e.g. Release 2022-04

  • All links are working and are helpful
  • Release is marked as “GA” and dates are correct
  • All relevant tickets are assigned
  • All assigned tickets are marked “Done” or pushed to the next release
  • Epics align with the “Highlights” of the release
  • Points to the correct “Release Sources Page” under “Downloads” e.g. Sources Release 2022-04 for Release 2022-04

Release Sources Page

e.g. Sources Release 2022-04

  • All components are consistently versioned according to Version management
  • All links are working and helpful
  • All components link to the correct repository and version
  • All components have correct “Release Notes”
  • All components link to reasonably similiar named repositories / package manager

Release Notes

  • Every effected component in the release specific sources page (e.g. Sources Release 2022-04) has an updated and complete change log in it’s repository

User Documentation

Installation Guide / Configuration / Other

Sandbox Landscape Sandbox Landscape

Findings Release 2022-04

  • No labels

Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk


This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/