...
- Review open issues in JIRA for the release. All issues should be resolved (with code committed) or moved to a future release.
- Update
Config/VERSION
, if not already updated, and make sure the version is defined in
.UpgradeVersionShell::$versions
- Merge changes from the hotfix release branch into
master
anddevelop
.- 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.
- If
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
- Notify the lead of the packaging/container team of the new tag.
- Wait for notification from the packaging/container team that packages/images are ready.
- Test the release, including upgrading QA servers and installing/deploying from scratch.
- Update download link at Directory Installation or Registry Installation - Source.
- Update TAP release page.
- If appropriate, flag the release in JIRA as "Released" with today's date.
- Create the next bug fix release in JIRA (#.#.#+1, unless there's a simultaneous feature release, in which case #.#+1.1).
- Update Release History.
- Update Home, including the Download link and About This Release.
- Update the COmanage Product Roadmap (if appropriate).
- Announce (to comanage-users, comanage-announce, and comanage-community). If appropriate and approved, credit additional funding sources.