Release 9.4.1

  • Cherry-pick merge requests labeled [Pick into Stable] for the current milestone (you can take advantage of the Pick into Stable 9.4 merged merge requests page) into the CE 9-4-stable and EE 9-4-stable-ee branches, respectively.

    • REFERENCE_TO_MR_TO_PICK

  • Merge CE 9-4-stable into EE 9-4-stable-ee following the [Merging a CE stable branch into its EE counterpart] guide

  • Sync stable branches: CE, EE, and Omnibus to dev, CE and Omnibus to github

  • Sync master branches to dev and github, as the CHANGELOG will be automatically updated on master during tagging

  • If needed, sync tags for dependencies (gitlab-shell, gitlab-workhorse, gitlab-pages, gitaly) to dev and github (when applicable)

  • Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.4.0-ee..9-4-stable-ee -- db/migrate db/post_migrate =>

  • Check omnibus-gitlab/9-4-stable CHANGELOG.md

  • Check omnibus-gitlab/9-4-stable-ee CHANGELOG.md

  • While waiting for tests to be green, now is a good time to start on the blog post: BLOG_POST_MR

  • Ensure tests are green on CE stable branch

  • Ensure tests are green on EE stable branch

  • Ensure tests are green on Omnibus CE stable branch

  • Ensure tests are green on Omnibus EE stable branch

  • In #releases: I'm going to tag 9.4.1

  • Tag the 9.4.1 version using the release task:

    ```sh
# In the release-tools project:
bundle exec rake "release[9.4.1]"
```

  • Check progress of EE packages build and CE packages build

  • In #production: I'm going to deploy 9.4.1 to staging

  • On video call, deploy release 9.4.1 to staging.gitlab.com sh # In the takeoff project: bundle exec rake "deploy[staging, 9.4.1-ee.0]"

  • In #production: I'm going to deploy 9.4.1 to canary

  • On video call, deploy release 9.4.1 to canary.gitlab.com sh # In the takeoff project: bundle exec rake "deploy[canary, 9.4.1-ee.0]"

  • In #production: I'm going to deploy 9.4.1 to production

  • Make sure to announce the deploy on Twitter and GitLab.com

    • With downtime: 1 hour before
    • Without downtime: 15 minutes before

  • On video call, deploy release 9.4.1 to GitLab.com sh # In the takeoff project: bundle exec rake "deploy[production, 9.4.1-ee.0]"

  • From the build pipeline, manually publish public packages

  • Verify that packages appear on packages.gitlab.com: EE / CE

  • Verify that Docker images appear on hub.docker.com: EE / CE

  • Create the 9.4.1 version on https://version.gitlab.com

  • Deploy the blog post

  • Tweet (prepare the Tweet text below or paste the tweet URL instead):

    ```
GitLab 9.4.1 is released! BLOG_POST_URL DESCRIPTION OF THE CHANGES
```

  • In the 9.4 Regressions issue:

    • Add the following notice:

      `9.4.1` has been tagged, further fixes will go into `9.4.2` as necessary.

    • Remove notes for the regressions fixed by version 9.4.1

  • Add omnibus-gitlab/9.4.1+ce.0 CHANGELOG.md items to omnibus-gitlab/master CHANGELOG.md

For references:

Edited by James Edwards-Jones