Dot Release Process

If a bug fix release is required, run through the below steps.

Release Timeline


  • 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.

A. (T-minus 4 working days) Code complete

  1. Release Manager:

    • Notify community about upcoming dot release through a Twitter announcement and in changelog with links to approved fixes and a date tagged as "TBD"

    • Open an issue in the GitLab Omnibus mentioning a dot release is coming. See example

    • Work with a developer to submit GitLab MR following this process and test the upgrade once the GitLab MR is merged and included in their RC

    • 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

  2. Dev:

    • 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

B. (T-minus 3 working days) Release Candidate Cut

  1. Build:

    • Verify with Release Manager before cutting any new dot release RCs (approved fixes should be merged)

C. (T-minus 2 working days) Release Candidate Testing

  1. QA:

    • If the dot release takes place during a regular release, update to dot-release RCs for the previous release and keep 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

D. (T-minus 0 working days) Release Build Cut

Once bug fix release is ready to cut:

  1. Dev:

    • 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

  2. Release Manager:

  3. Marketing: