Page History

...

1. Check for latest version of dependent libraries and update if needed.
2. Review open issues in JIRA for the release. All issues should be resolved (with code committed) or moved to a future release.
3. Update Config/VERSION, if not already updated, and make sure the version is defined in UpgradeVersionShell::$versions.

4. Merge develop into master (assuming you're already following both)

   Code Block
   $ git checkout develop $ git pull origin $ git checkout master $ git pull origin $ git merge develop (Make sure everything looks OK) $ git push origin master

   
   

5. Test the release, including upgrading QA servers and installing from scratch.

6. Tag the release:

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

   
   

7. Update download link at Directory Installation or Registry Installation - Source.
8. Review Registry Data Model and update the status of tables as appropriate.
9. In JIRA, flag the release as "Released" with today's date.
10. Update Release History.
11. Update Home, including the Download link and About This Release.
12. Update the COmanage Product Roadmap.
13. If there are any unrelated bug fixes in the prior hotfix series (#.#-1.#), simultaneously release that as the "last maintenance release" of the previous series.
14. Announce (to comanage-users, comanage-announce, and comanage-community). If appropriate and approved, credit additional funding sources.

...

A bug release is intended to quickly fix bugs discovered with a standard release. These releases are indicated using a revision number after the related standard release number. There is not necessarily a corresponding JIRA release.

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. Merge changes from the hotfix release branch into master and develop.
   1.  If master has moved on to a new minor release, do not merge into either branch. You may wish to cherry pick commits if appropriate.

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

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

   
   

5. Update download link at Directory Installation or Registry Installation - Source.
6. If appropriate, flag the release in JIRA as "Released" with today's date.
7. Create the next bug fix release in JIRA (#.#.#+1, unless there's a simultaneous feature release, in which case #.#+1.1).
8. Update Release History.
9. Update Home, including the Download link and About This Release.
10. Update the COmanage Product Roadmap.
    
11. Announce (to comanage-users, comanage-announce, and comanage-community). If appropriate and approved, credit additional funding sources.