Skip to content
GitLab Next
Closed
Created by Rubén Dávila@rdavilaContributor110 of 124 tasks completed110/124 tasks

Release 8.11

29th: (16 working days before the 22nd)

1st: (15 working days before the 22nd)

RC1

Anytime between 1st (15 working days before the 22nd) and 16th (4 working days before the 22nd)

Copy-paste the tasks below for any other RCs (be sure to update the RC number).

RC2

Only after the 11th (7 working days before the 22nd)

  • Tweet about the 8.11.0-rc2 release:

    ```
GitLab 8.11.0-rc2 is available: https://packages.gitlab.com/gitlab/unstable
Use at your own risk. Please link regressions issues from
LINK_TO_REGRESSION_ISSUE
```

11th: (7 working days before the 22nd)

Anytime between 17th (3 working days before the 22nd) and 19th (1 working day before the 22nd)

  • In #core:

    @developers

TL;DR: Ensure the `8.11.0` milestone and the `Pick into Stable` label are set, no need to ping me.

From now on, please follow the "Change for stable release" process:
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#changes-for-stable-releases

Copy-paste the tasks below for any other RCs (be sure to update the RC number).

RC3

RC4

RC5

RC6

RC7

17th: (3 working days before the 22nd)

  • Check that everyone is mentioned on the blog post using @all:

    ```
Hello @all, this is the monthly release post that will go out on the 22nd,
announcing the new GitLab version. Look through it to see if we can make any
changes and feel free to comment with suggestions or questions!
```

or, if the blog post is still very much a work in progress:

```
Hello @all, this is the merge request for the monthly release post that will
go out on the 22nd, announcing the new GitLab version. Right now it's all
boilerplate, but feel free to remind us about things that shouldn't be left
out!
```

18th: (2 working days before the 22nd)

  • Ask in #core for suggestions about who should be this release's MVP. Once chosen, add them to the blog post and to the MVP page, in the same merge request

19th: (1 working day before the 22nd)

Ideally, the last RC should be released no later than this day and should point to the same commit as the final release.

22nd before 1200 CET:

Release before 1200 CET / 2AM PST, to make sure the majority of our users get the new version on the 22nd and there is sufficient time in the European workday to quickly fix any issues.

  • Before 0800 PDT / 1700 CET:

    • Remove (unreleased) from CHANGELOG and add a (unreleased) line for the next patch

    • Remove (unreleased) from CHANGELOG-EE and add a (unreleased) line for the next patch

    • Merge CE 8-11-stable into EE 8-11-stable-ee following the Merging a CE stable branch into its EE counterpart guide

    • Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.11.0-rc3-ee..8-11-stable-ee -- db/migrate =>

    • Sync CE, EE, and Omnibus to dev

    • Ensure tests are green on CE

    • Ensure tests are green on EE

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

    • Tag the 8.11.0 version using the release task:

      ```sh
bundle exec rake "release[8.11.0]"
```

    • Check that EE packages are built, CE packages are built and appears on packages.gitlab.com: EE / CE

    • Update the version in the VERSION file to 8.12.0-pre and create the v8.12.0.pre tag:

      echo "8.12.0-pre" > VERSION
git add VERSION && git ci # ci = commit --gpg-sign --signoff --verbose
git pdog # pdog = push dev,origin,github
git tag -s v8.12.0.pre -m "Update VERSION to 8.12.0.pre"
git pdog v8.12.0.pre:v8.12.0.pre

  • Before 0900 PDT / 1800 CET:

  • At 1000 PDT / 1900 CET:

    • Publish the release blog post
    • Ensure someone tweets about the 8.11.0 release
    • Upgrade the #gitlab channel's topic on IRC Freenode with the latest version number