Page History

Standard Release (#.#)

1. Merge develop into master

   Code Block
   $ git fetch origin $ git checkout -b develop origin/develop $ git merge master (Make sure everything looks OK) $ git checkout master $ git merge develop $ git push origin master

2. Test the release against the current demo script to make sure nothing critical to the demo broke.
3. Check for latest version of dependent libraries and update if needed.
4. Review open issues in JIRA for the release. All issues should be resolved (with code committed) or moved to a future release.
5. Update Config/VERSION
6. Tag the release: Update for git

   Code Block
   svngit copy https://svn.internet2.edu/svn/comanage/registry/trunk https://svn.internet2.edu/svn/comanage/registry/tags/0tag -a 0.8.5 -m 'COmanage "Tag 0Registry v0.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.

...

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. Merge changes into master
2. Update Config/VERSION
3. Tag the release: Update for git

   Code Block
   svngit copy https://svn.internet2.edu/svn/comanage/registry/trunk https://svn.internet2.edu/svn/comanage/registry/tags/0.5.1tag -a 0.8.5 -m "Tag 0.5.1"'COmanage Registry v0.8.5'

4. Update download link at Directory Installation or Registry Installation - Source.
5. If appropriate, flag the release in JIRA as "Released" with today's date.
6. Update Release History.
7. Update Home.
8. Announce.