Page History

...

1. Review open issues in JIRA for the release. All issues should be resolved (with code committed) or moved to a future release.
2. Update Config/VERSION, if not already updated, and make sure the version is defined in UpgradeVersionShell::$versions.
3. Update the LABEL in the file container/aws_buildspec.yml to the intended release number.
4. Merge changes from the hotfix release branch into main and develop.
   1.  If main has moved on to a new minor release, do not merge into either branch. You may wish to cherry pick commits if appropriate.

5. Tag the release from the hotfix branch (though you can also use main if you merged the hotfix branch into main):

   Code Block
   git tag -a 0.8.5 -m 'COmanage Registry v0.8.5' $ git push origin 0.8.5

   
   

6. Notify the lead of the packaging/container team of the new tag.
7. The lead of the packaging/container team builds new container images.
8. Wait for notification from the packaging/container team that packages/images are ready.
9. Test the release, including upgrading QA servers and installing/deploying from scratch.
10. Update download link at Directory Installation, Registry Installation - Source, or Match Installation - Source.
11. Update TAP release page.
12. If appropriate, flag the release in JIRA as "Released" with today's date.
13. Create the next bug fix release in JIRA (#.#.#+1, unless there's a simultaneous feature release, in which case #.#+1.1).
14. Update Release History.
15. Update Home, including the Download link and About This Release.
16. Update the COmanage Product Roadmap (if appropriate).
    
17. Announce (to comanage-users and comanage-announce). If appropriate and approved, credit additional funding sources.