Page History

Release Candidate (#.#.0-rc.#)

The steps for the Release Candidates are the same as for the Standard Releases, up to and including the tagging of the release. Do not update the public links, and only announce informally.

Update Config/VERSION to include the rc label.

Standard Release (#.#.0)

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 against the current demo script to make sure nothing critical to the demo broke.

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. In JIRA, flag the release as "Released" with today's date.
9. Update Release History.
10. Update Home.
11. Announce.

...