If a bug fix release is required, run through the below steps.
All cut-off dates are based on 10am (San Francisco Time) on the day stated.
T-minus counts are measured in "working days" (weekdays other than major holidays concurrent in US and Canada) prior to release day.
Notify community about upcoming dot release through a Twitter announcement and in changelog with links to approved fixes and a date tagged as "TBD"
Make a post in Announcements channel announcing the dot release to the rest of the team with links to approved tickets and include a link to the ticket to submit the GitLab MR
PRs for hotfixes are made to release branch
Review PRs made from release branch and merge changes into the release branch as required and merge the release branch back into master once per day
Verify with Release Manager before cutting any new dot release RCs (approved fixes should be merged)
If the dot release takes place during a regular release, update
prev.test.mattermost.com to dot-release RCs for the previous release and keep
rc.test.mattermost.com on the latest regular release version
Test the new RC to verify fixes merged to the release branch work
Post in Release Discussion channel after testing
Once bug fix release is ready to cut:
Tag a new release (e.g. 1.1.1) and run an official build
Verify hashes and GPG signatures are correct, once build is cut
Delete RCs after final version is shipped
Merge the Changelog PR with notes on patch releases (see example entry)
Update the version archive
Update the Extended Support Release documentation if needed
Update Mattermost server download page with the links to the EE and TE bits
Test the download links before and after updating the page
Confirm that mattermost-docker has been updated to the latest version (contact the maintainer via direct message on community server if necessary)