Release 9.3

First working day after 7th

Stable branch should be created after the 7th. The 7th is the last date to reliably get things in.

• In #development:

  ```
  @channel
  
  I am about to create the `9-3-stable` branch. Everything merged into `master`
  after this point will go into next month's release. Only regression and security fixes
  will be cherry-picked into `9-3-stable`.
  
  Please ensure that merge requests have the correct milestone (`9.3` for this release)
  and the `Pick into Stable` label.
  
  From now on, please follow the "After the 7th" process:
  https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md#after-the-7th
  ```

• Create branch 9-3-stable from CE 9-2-stable manually

• Create branch 9-3-stable-ee from EE 9-2-stable-ee manually

• In Omnibus create both 9-3-stable and 9-3-stable-ee from 9-2-stable manually

• Merge GitLab CE into EE on the stable branches

• Sync CE, EE, and Omnibus to dev

RC1

• Ensure omnibus-gitlab is ready to build packages by asking the Omnibus maintainers

• Follow the Creating RC1 guide:

  • Pick https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10885 into 9-3-stable as planned in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10885#note_30026564

  • Merge 9-3-stable into 9-3-stable-ee, sync to all remotes and ensure Pipeline is green

  • Create MR on CE master updating the "Installation from Source" guide, creating the "Update" guides. https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12038

  • Create MR on EE master creating the "CE to EE" guides https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2101

  • Create MR on CE master updating the gitignore and license templates https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12041

  • Create MR on CE master updating the dependencies license list https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12042

  • [ ] Ensure above MRs are merged and marked Pick into Stable for milestone 9.3 Not required for RC1 as per https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10885#note_30026564

  • [ ] Cherry-pick merge requests labeled Pick into Stable for the current milestone (you can take advantage of the Pick into Stable 9.3 merged merge requests page) into the CE 9-3-stable and EE 9-3-stable-ee branches, respectively. Not required for RC1 as per https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10885#note_30026564

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

  • Sync CE, EE, and Omnibus to dev

  • Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.2.5-ee..9-3-stable-ee -- db/migrate db/post_migrate => https://gitlab.com/gitlab-org/gitlab-ce/snippets/1664431

  • 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

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

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

  • In #releases: I'm going to tag 9.3.0-rc1

  • Tag the 9.3.0-rc1 version using the release task:

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

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

  • In #production: I'm going to deploy 9.3.0-rc1 to staging sh # In the chef-repo project: bundle exec rake "deploy[staging, 9.3.0-rc1.ee.0]"

  • Do the deploy of 9.3.0-rc1 to staging.gitlab.com

  • In #production: I'm going to deploy 9.3.0-rc1 to production sh # In the chef-repo project: bundle exec rake "deploy[production, 9.3.0-rc1.ee.0]"

  • Tweet about the deploy, at this point the deploy alert banner on GitLab.com should already be up.

  • Do the deploy of 9.3.0-rc1 to GitLab.com

  • Post a tweet about the 9.3.0-rc1 release:

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

• Create the regression issue in the CE issue tracker using the regression_issue task and bookmark it:

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

• Prepare the blog post using the new_release_post task, in the www-gitlab-com project:

  ```sh
  # In the www-gitlab-com project:
  bundle exec rake "new_release_post[9.3]"
  ```

RC2

• Merge CE master into 9-3-stable till commit https://gitlab.com/gitlab-org/gitlab-ce/commit/b1bf6d88fceb24663bfe4be2d9cc111710d9126b (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12073)

• Merge EE master into 9-3-stable-ee till commit https://gitlab.com/gitlab-org/gitlab-ee/commit/86051969bd10f2c75540add61424aa12bb21e265 (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2106)

• Ensure https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12041 changes are matching to generated changes when bin/rake gitlab:update_templates is run on 9-3-stable. As per Release doc.

  • MR updated with https://gitlab.com/gitlab-org/gitlab-ce/commit/971e81257d1a7135b76ffaea2c1a7e9aad5a5e40.

• Ensure https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12042 changes are matching to generated changes when bin/bundle exec license_finder report --format=csv --save=vendor/licenses.csv is run on 9-3-stable. As per Release doc.

  • MR updated with https://gitlab.com/gitlab-org/gitlab-ce/commit/139ef4207f0cf317b241ee1c35b2eb8645b5dc96.

• Make sure following MRs are merged into master;

  • https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2101
  • https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12038
  • https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12041
  • https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12042

• Cherry-pick merge requests labeled Pick into Stable for the current milestone (you can take advantage of the Pick into Stable 9.3 merged merge requests page) into the CE 9-3-stable and EE 9-3-stable-ee branches, respectively. All regressions for %9.3 will go in RC3 except for critical MRs.

  • https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12048
  • https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12109

• Follow the Creating subsequent RCs guide for 9.3.0-rc2:

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

  • Sync CE, EE, and Omnibus to dev

  • Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.3.0-rc1-ee..9-3-stable-ee -- db/migrate db/post_migrate => https://gitlab.com/snippets/1665149

  • 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

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

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

  • In #releases: I'm going to tag 9.3.0-rc2

  • Tag the 9.3.0-rc2 version using the release task:

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

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

• In #production: I'm going to deploy 9.3.0-rc2 to staging sh # In the chef-repo project: bundle exec rake "deploy[staging, 9.3.0-rc2.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc2 to staging.gitlab.com

• In #production: I'm going to deploy 9.3.0-rc2 to production sh # In the chef-repo project: bundle exec rake "deploy[production, 9.3.0-rc2.ee.0, gitlab/unstable]"

• Tweet about the deploy, at this point the deploy alert banner on GitLab.com should already be up.

• Do the deploy 9.3.0-rc2 to GitLab.com

• Post a tweet about the 9.3.0-rc2 release:

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

• RC2 couldn't be deployed due to post-migrations related problem as discussed here https://gitlab.com/gitlab-org/gitlab-ce/issues/33736#note_32561501

RC3

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

• Follow the Creating subsequent RCs guide for 9.3.0-rc3:

  • Merge CE 9-3-stable into EE 9-3-stable-ee following the Merging a CE stable branch into its EE counterpart guide, Not required as we picked only fixes for post-deployment migrations into EE for the issues we faced in RC2.

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

  • Sync CE, EE, and Omnibus to dev

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

  • Tag the 9.3.0-rc3 version using the release task:

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

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

• In #production: I'm going to deploy 9.3.0-rc3 to staging sh # In the chef-repo project: bundle exec rake "deploy[staging, 9.3.0-rc3.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc3 to staging.gitlab.com

• In #production: I'm going to deploy 9.3.0-rc3 to production sh # In the chef-repo project: bundle exec rake "deploy[production, 9.3.0-rc3.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc3 to GitLab.com

• Tweet about the 9.3.0-rc3 release:

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

RC4

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

• Ensure https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12260 is merged (9-3-stable-rc4 => 9-3-stable)

• Ensure https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2161 is merged (9-3-stable-ee-rc4 => 9-3-stable-ee)

• Follow the Creating subsequent RCs guide for 9.3.0-rc4:

  • Merge CE 9-3-stable into EE 9-3-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 v9.3.0-rc3-ee..9-3-stable-ee -- db/migrate db/post_migrate =>

  • Sync CE, EE, and Omnibus to dev

  • 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 (Will stay red until next RC because it uses last tag)

  • Ensure tests are green on Omnibus EE stable branch (Will stay red until next RC because it uses last tag)

  • In #releases: I'm going to tag 9.3.0-rc4

  • Tag the 9.3.0-rc4 version using the release task:

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

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

• In #production: I'm going to deploy 9.3.0-rc4 to staging sh # In the chef-repo project: bundle exec rake "deploy[staging, 9.3.0-rc4.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc4 to staging.gitlab.com

• In #production: I'm going to deploy 9.3.0-rc4 to production sh # In the chef-repo project: bundle exec rake "deploy[production, 9.3.0-rc4.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc4 to GitLab.com

• Tweet about the 9.3.0-rc4 release:

  ```
  GitLab 9.3.0-rc4 is available: https://packages.gitlab.com/gitlab/unstable
  Use at your own risk. Please link regressions issues from
  https://gitlab.com/gitlab-org/gitlab-ce/issues/33531
  ```

RC5

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

• Follow the Creating subsequent RCs guide for 9.3.0-rc5:

  • Merge CE 9-3-stable into EE 9-3-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 v9.3.0-rc1-ee..9-3-stable-ee -- db/migrate db/post_migrate =>

  • Sync CE, EE, and Omnibus to dev

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

  • Tag the 9.3.0-rc5 version using the release task:

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

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

• In #production: I'm going to deploy 9.3.0-rc5 to staging sh # In the chef-repo project: bundle exec rake "deploy[staging, 9.3.0-rc5.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc5 to staging.gitlab.com

• [ ] In #production: I'm going to deploy 9.3.0-rc5 to production sh # In the chef-repo project: bundle exec rake "deploy[production, 9.3.0-rc5.ee.0, gitlab/unstable]"

• [ ] Deploy 9.3.0-rc5 to GitLab.com

• [ ] Tweet about the 9.3.0-rc5 release:

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

RC5 was reverted because of merge requests regression, see https://gitlab.com/gitlab-org/gitlab-ce/issues/33999 for more details

RC6

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

• Follow the Creating subsequent RCs guide for 9.3.0-rc6:

  • Merge CE 9-3-stable into EE 9-3-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 v9.3.0-rc1-ee..9-3-stable-ee -- db/migrate db/post_migrate =>

  • Sync CE, EE, and Omnibus to dev

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

  • Tag the 9.3.0-rc6 version using the release task:

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

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

• In #production: I'm going to deploy 9.3.0-rc6 to staging sh # In the chef-repo project: bundle exec rake "deploy[staging, 9.3.0-rc6.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc6 to staging.gitlab.com

• In #production: I'm going to deploy 9.3.0-rc6 to production sh # In the chef-repo project: bundle exec rake "deploy[production, 9.3.0-rc6.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc6 to GitLab.com

• Tweet about the 9.3.0-rc6 release:

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

RC7

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

• Follow the Creating subsequent RCs guide for 9.3.0-rc7:

  • Merge CE 9-3-stable into EE 9-3-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 v9.3.0-rc1-ee..9-3-stable-ee -- db/migrate db/post_migrate =>

  • Sync CE, EE, and Omnibus to dev

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

  • Tag the 9.3.0-rc7 version using the release task:

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

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

• In #production: I'm going to deploy 9.3.0-rc7 to staging sh # In the chef-repo project: bundle exec rake "deploy[staging, 9.3.0-rc7.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc7 to staging.gitlab.com

• In #production: I'm going to deploy 9.3.0-rc7 to production sh # In the chef-repo project: bundle exec rake "deploy[production, 9.3.0-rc7.ee.0, gitlab/unstable]"

• Deploy 9.3.0-rc7 to GitLab.com

• Tweet about the 9.3.0-rc7 release:

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

QA

• Determine QA person and notify this person: MENTION_THIS_PERSON_HERE
• Do QA and fix anything coming out of it: LINK_TO_QA_ISSUE

Anytime after RC1 but before 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!
  ```

• 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

• Create another RC as needed.

Keep in mind that:

1. After feature freeze only regression and security fixes can be cherry-picked into 9-3-stable.
2. Last RC should point to the same commit as the final release.

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

#### RC3

- [ ] Cherry-pick merge requests labeled [`Pick into Stable`] for the current
  milestone (you can take advantage of the
  [`Pick into Stable` 9.3 merged merge requests] page) into
  the CE `9-3-stable` and EE `9-3-stable-ee`
  branches, respectively.
- Follow the [Creating subsequent RCs] guide for `9.3.0-rc3`:
  - [ ] Merge CE `9-3-stable` into EE `9-3-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 v9.3.0-rc1-ee..9-3-stable-ee -- db/migrate db/post_migrate` =>
  - [ ] Sync CE, EE, and Omnibus to `dev`
  - [ ] 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.3.0-rc3`
  - [ ] Tag the `9.3.0-rc3` version using the [`release` task]:

        ```sh
        # In the release-tools project:
        bundle exec rake "release[9.3.0-rc3]"
        ```
- [ ] Check that [EE packages are built], [CE packages are built] and appears on `packages.gitlab.com`: [EE & CE](https://packages.gitlab.com/app/gitlab/unstable/search?q=9.3.0-rc3)
- [ ] In `#production`: I'm going to deploy `9.3.0-rc3` to staging
      ```sh
      # In the chef-repo project:
      bundle exec rake "deploy[staging, 9.3.0-rc3.ee.0, gitlab/unstable]"
      ```
- [ ] [Deploy] [`9.3.0-rc3`](https://packages.gitlab.com/gitlab/unstable/packages/ubuntu/xenial/gitlab-ee_9.3.0-rc3.ee.0_amd64.deb) to [staging.gitlab.com]
- [ ] In `#production`: I'm going to deploy `9.3.0-rc3` to production
      ```sh
      # In the chef-repo project:
      bundle exec rake "deploy[production, 9.3.0-rc3.ee.0, gitlab/unstable]"
      ```
- [ ] [Deploy] [`9.3.0-rc3`](https://packages.gitlab.com/gitlab/unstable/packages/ubuntu/xenial/gitlab-ee_9.3.0-rc3.ee.0_amd64.deb) to GitLab.com
- [ ] Tweet about the `9.3.0-rc3` release:

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

22nd before 15:00 UTC:

No new code is added to release that was not included in the last RC. This way we ensure the release does not introduce new regressions.

• Before 13:00 UTC:

  • Sync CE, EE, and Omnibus to dev

  • 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

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

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

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

  • Tag the 9.3.0 version using the release task:

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

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

• Before 14:00 UTC:

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

  • Do the deploy of 9.3.0 to staging.gitlab.com

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

  • Tweet about the deploy, at this point the deploy alert banner on GitLab.com should already be up.

  • Do the deploy of 9.3.0 to GitLab.com

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

  • Create the first patch issue using the patch_issue task:

    # In the release-tools project:
    bundle exec rake "patch_issue[9.3.1]"

• At 15:00 UTC:

  • Publish the release blog post
  • Ensure someone tweets about the 9.3.0 release

/cc @timothyandrew @selfup @ClemMakesApps

changed the description

marked the checklist item In #development: as completed

changed the description

changed the description

marked the checklist item Create branch 9-3-stable from CE 9-2-stable manually as completed

marked the checklist item Create branch 9-3-stable-ee from EE 9-2-stable-ee manually as completed

marked the checklist item Merge [GitLab CE into EE] on the stable branches as completed

changed the description

marked the checklist item Pick https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10885 into 9-3-stable as planned in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10885#note_30026564 as completed

marked the checklist item Merge 9-3-stable into 9-3-stable-ee, sync to all remotes and ensure Pipeline is green as completed

9-3-stable has been green most of today.

We've been waiting for 9-3-stable-ee to get green.

@mkozono and @dbalexandre are working on that in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2095

assigned to @ClemMakesApps

That MR merged. We are now waiting for https://gitlab.com/gitlab-org/gitlab-ee/commits/9-3-stable-ee to get green

@grzesiek FYI, 9.3 RC1 will just be 9-2-stable + the project auth MR (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10885#note_30026564). The release managers should probably schedule RC2 with you regarding https://gitlab.com/gitlab-com/infrastructure/issues/1977.

Sure, thanks for the heads up @stanhu!

changed the description

marked the checklist item In Omnibus create both 9-3-stable and 9-3-stable-ee from 9-2-stable manually as completed

marked the checklist item Sync CE, EE, and Omnibus to dev as completed

changed the description

changed the description

changed the description

changed the description

changed the description

marked the checklist item In #releases: I'm going to tag 9.3.0-rc1 as completed

marked the checklist item Tag the 9.3.0-rc1 version using the [release task]: as completed

changed the description

marked the checklist item Ensure omnibus-gitlab is ready to build packages by asking the Omnibus maintainers as completed

changed the description

marked the checklist item Check that [EE packages are built], [CE packages are built] and appears on packages.gitlab.com: EE & CE as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc1 to staging as completed

changed the description

marked the checklist item Do the [deploy] of 9.3.0-rc1 to [staging.gitlab.com] as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc1 to production as completed

changed the description

marked the checklist item Tweet about the deploy, at this point the deploy alert banner on GitLab.com should already be up. as completed

Release post is https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/5804

Regression issue is https://gitlab.com/gitlab-org/gitlab-ce/issues/33531

assigned to @mikegreiling and @jamedjo

changed the description

changed the description

Created https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12073 to merge master into 9-3-stable

marked the checklist item Do the [deploy] of 9.3.0-rc1 to GitLab.com as completed

marked the checklist item Post a [tweet about] the 9.3.0-rc1 release: as completed

marked the checklist item Create the [regression issue] in the CE issue tracker using the [regression_issue task] and bookmark it: as completed

marked the checklist item Prepare the [blog post] using the [new_release_post task], in the [www-gitlab-com project]: as completed

changed the description

changed the description

marked the checklist item Merge CE master into 9-3-stable till commit https://gitlab.com/gitlab-org/gitlab-ce/commit/b1bf6d88fceb24663bfe4be2d9cc111710d9126b (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12073) as completed

changed the description

marked the checklist item Merge EE master into 9-3-stable-ee till commit https://gitlab.com/gitlab-org/gitlab-ee/commit/86051969bd10f2c75540add61424aa12bb21e265 as completed

changed the description

changed the description

marked the checklist item Ensure https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12041 changes are matching to generated changes when bin/rake gitlab:update_templates is run on 9-3-stable. As per Release doc. as completed

marked the checklist item Ensure https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12042 changes are matching to generated changes when bin/bundle exec license_finder report --format=csv --save=vendor/licenses.csv is run on 9-3-stable. As per Release doc. as completed

marked the checklist item https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12048 as completed

changed the description

marked the checklist item ~~Cherry-pick merge requests labeled [Pick into Stable] for the current as completed

changed the description

marked the checklist item Merge CE 9-3-stable into EE 9-3-stable-ee following the [Merging a CE stable branch into its EE counterpart] guide as completed

marked the checklist item Sync CE, EE, and Omnibus to dev as completed

marked the checklist item Ensure tests are green on [CE stable branch] as completed

marked the checklist item Ensure tests are green on [EE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus CE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus EE stable branch] as completed

changed the description

mentioned in issue #31499 (closed)

changed the description

marked the checklist item In #releases: I'm going to tag 9.3.0-rc2 as completed

marked the checklist item Tag the 9.3.0-rc2 version using the [release task]: as completed

changed the description

marked the checklist item Check that [EE packages are built], [CE packages are built] and appears on packages.gitlab.com: EE & CE as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc2 to staging as completed

We found a MR that caused the login input box to disappear.

1. We are reverting https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11842 in CE and EE master
2. We will cherry-pick that commit into 9-3-stable and 9-3-stable-ee
3. Tag and deploy

More details at https://gitlab.com/gitlab-org/gitlab-ce/issues/33736#note_32561501

marked the checklist item Ensure tests are green on [Omnibus EE stable branch] as completed

changed the description

marked the checklist item Ensure tests are green on [EE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus CE stable branch] as completed

marked the checklist item In #releases: I'm going to tag 9.3.0-rc3 as completed

changed the description

marked the checklist item Sync CE, EE, and Omnibus to dev as completed

marked the checklist item Ensure tests are green on [CE stable branch] as completed

marked the checklist item Tag the 9.3.0-rc3 version using the [release task]: as completed

Migrations:

== 20170427103502 CreateWebHookLogs: migrated (0.3056s) =======================
== 20170502065653 MakeAutoCancelPendingPipelinesOnByDefault: migrated (0.2530s)
== 20170502135553 CreateIndexCiPipelinesAutoCanceledById: migrated (31.4294s) =
== 20170502140503 CreateIndexCiBuildsAutoCanceledById: migrated (99.2308s) ====
== 20170503023315 AddRepositoryUpdateEventsToWebHooks: migrated (2.4809s) =====
== 20170503114228 AddDescriptionToSnippets: migrated (0.0196s) ================
== 20170505133904 UpdateGeoNodesSystemHooks: migrated (0.0266s) ===============
== 20170507205316 AddHeadPipelineIdToMergeRequests: migrated (0.0040s) ========
== 20170508153950 AddNotNullContraintsToCiVariables: migrated (0.3183s) =======
== 20170508190732 AddForeignKeyToCiVariables: migrated (2.3895s) ==============
== 20170509153720 CreateProjectMirrorData: migrated (31.0663s) ================
== 20170511082759 RenameWebHooksBuildEventsToJobEvents: migrated (3.2966s) ====
== 20170511083824 RenameServicesBuildEventsToJobEvents: migrated (329.3728s) ==
== 20170512131952 AddPlanToNamespace: migrated (0.0014s) ======================
== 20170512173638 AddCheckNamespacePlanToApplicationSettings: migrated (0.0695s)
== 20170513005817 AddPushRuleBranchName: migrated (0.0012s) ===================
== 20170515093334 AddMirrorSettingsToApplicationSetting: migrated (0.1917s) ===
== 20170519102115 AddPrometheusSettingsToMetricsSettings: migrated (0.0582s) ==
== 20170521184006 AddChangePositionToNotes: migrated (1.0018s) ================
== 20170522194603 CreateGeoRepositoryUpdatedEvents: migrated (1.1832s) ========
== 20170522201800 CreateGeoEventLog: migrated (0.1284s) =======================
== 20170523091700 AddRssTokenToUsers: migrated (5.7277s) ======================
== 20170523121229 CreateConversationalDevelopmentIndexMetrics: migrated (0.0382s)
== 20170524125940 AddSourceToCiPipeline: migrated (0.0125s) ===================
== 20170524161101 AddProtectedToCiVariables: migrated (2.9008s) ===============
== 20170525132202 CreatePipelineStages: migrated (0.7705s) ====================
== 20170525174156 CreateFeatureTables: migrated (0.2611s) =====================
== 20170525174157 CreatePipelineSourcePipeline: migrated (0.0429s) ============
== 20170525174158 AddCiPipelineSourcePipelineIndexes: migrated (0.6240s) ======
== 20170525174159 AddCiPipelineSourcePipelineForeignKey: migrated (1.6918s) ===
== 20170526185602 AddStageIdToCiBuilds: migrated (104.8695s) ==================
== 20170531180233 AddAuthorizedKeysEnabledToApplicationSettings: migrated (0.0016s)
== 20170531202042 RenameUsersLdapEmailToExternalEmail: migrated (1399.6063s) ==
== 20170602003304 AddCloneUrlPrefixToGeoNode: migrated (0.0012s) ==============
== 20170603200744 AddEmailProviderToUsers: migrated (0.1538s) =================

Downtime caused by RenameUsersLdapEmailToExternalEmail that locked the users table for ~23 minutes

RC3 deployment on Production

20170502070007 EnableAutoCancelPendingPipelinesForAll

Timed out while running deploy script for production, but went fine when ran

bundle exec knife ssh -a ipaddress 'roles:gitlab-base-deploy-node' 'sudo gitlab-rake db:migrate'

Independently.

RC3 deployment to Production

Post-deployment migrations failed with Deadlock when ran with bundle exec knife ssh -a ipaddress 'roles:gitlab-base-deploy-node' 'sudo gitlab-rake db:migrate', here's log;

execute("UPDATE \"merge_requests\" SET \"head_pipeline_id\" = ((SELECT max(\"ci_pipelines\".\"id\") FROM \"ci_pipelines\" WHERE \"ci_pipelines\".\"ref\" = \"merge_requests\".\"source_branch\" AND \"ci_pipelines\".\"project_id\" = \"merge_requests\".\"source_project_id\")) WHERE \"merge_requests\".\"id\" >= 1851858 AND \"merge_requests\".\"id\" < 2036102")
52.177.192.107 rake aborted!
52.177.192.107 StandardError: An error has occurred, this and all later migrations canceled:
52.177.192.107 
52.177.192.107 PG::TRDeadlockDetected: ERROR:  deadlock detected
52.177.192.107 DETAIL:  Process 51504 waits for ShareLock on transaction 741281723; blocked by process 29878.
52.177.192.107 Process 29878 waits for ShareLock on transaction 741251373; blocked by process 51504.
52.177.192.107 HINT:  See server log for query details.
52.177.192.107 CONTEXT:  while updating tuple (166628,28) in relation "merge_requests"
52.177.192.107 : UPDATE "merge_requests" SET "head_pipeline_id" = ((SELECT max("ci_pipelines"."id") FROM "ci_pipelines" WHERE "ci_pipelines"."ref" = "merge_requests"."source_branch" AND "ci_pipelines"."project_id" = "merge_requests"."source_project_id")) WHERE "merge_requests"."id" >= 1851858 AND "merge_requests"."id" < 2036102/opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:231:in `block in update_column_in_batches'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:208:in `loop'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:208:in `update_column_in_batches'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/db/post_migrate/20170508170547_add_head_pipeline_for_each_merge_request.rb:20:in `up'
52.177.192.107 /opt/gitlab/embedded/bin/bundle:22:in `load'
52.177.192.107 /opt/gitlab/embedded/bin/bundle:22:in `<main>'
52.177.192.107 ActiveRecord::StatementInvalid: PG::TRDeadlockDetected: ERROR:  deadlock detected
52.177.192.107 DETAIL:  Process 51504 waits for ShareLock on transaction 741281723; blocked by process 29878.
52.177.192.107 Process 29878 waits for ShareLock on transaction 741251373; blocked by process 51504.
52.177.192.107 HINT:  See server log for query details.
52.177.192.107 CONTEXT:  while updating tuple (166628,28) in relation "merge_requests"
52.177.192.107 : UPDATE "merge_requests" SET "head_pipeline_id" = ((SELECT max("ci_pipelines"."id") FROM "ci_pipelines" WHERE "ci_pipelines"."ref" = "merge_requests"."source_branch" AND "ci_pipelines"."project_id" = "merge_requests"."source_project_id")) WHERE "merge_requests"."id" >= 1851858 AND "merge_requests"."id" < 2036102
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:231:in `block in update_column_in_batches'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:208:in `loop'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:208:in `update_column_in_batches'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/db/post_migrate/20170508170547_add_head_pipeline_for_each_merge_request.rb:20:in `up'
52.177.192.107 /opt/gitlab/embedded/bin/bundle:22:in `load'
52.177.192.107 /opt/gitlab/embedded/bin/bundle:22:in `<main>'
52.177.192.107 PG::TRDeadlockDetected: ERROR:  deadlock detected
52.177.192.107 DETAIL:  Process 51504 waits for ShareLock on transaction 741281723; blocked by process 29878.
52.177.192.107 Process 29878 waits for ShareLock on transaction 741251373; blocked by process 51504.
52.177.192.107 HINT:  See server log for query details.
52.177.192.107 CONTEXT:  while updating tuple (166628,28) in relation "merge_requests"
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:231:in `block in update_column_in_batches'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:208:in `loop'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/database/migration_helpers.rb:208:in `update_column_in_batches'
52.177.192.107 /opt/gitlab/embedded/service/gitlab-rails/db/post_migrate/20170508170547_add_head_pipeline_for_each_merge_request.rb:20:in `up'
52.177.192.107 /opt/gitlab/embedded/bin/bundle:22:in `load'
52.177.192.107 /opt/gitlab/embedded/bin/bundle:22:in `<main>'
52.177.192.107 Tasks: TOP => db:migrate
52.177.192.107 (See full trace by running task with --trace)

This MR is not picked to %9.3 stable, thus all pipelines that do depend on dependencies do not work: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12113

• we had to stop Sidekiq in order to avoid dead locks on migrations
• important CI/CD bug fix was not correctly picked into RC3

RC3 Deployment

To prevent deadlock failure as mentioned in https://gitlab.com/gitlab-org/gitlab-ce/issues/33452#note_32714566

Sidekiq needs to be stopped before running post-deployment migrations.

• deployment call has been terminated several times because of not-a-premium account

I looked at the migration logs, and the function/trigger is not the problem:

   -> 0.0227s
-- execute("CREATE TRIGGER trigger_f07461f2dbe8\nBEFORE INSERT OR UPDATE\nON \"users\"\nFOR EACH ROW\nEXECUTE PROCEDURE trigger_f07461f2dbe8()\n")
   -> 0.0181s
-- exec_query("SELECT COUNT(*) AS count FROM \"users\"")
   -> 0.1646s

Instead there's this:

-- change_column_null(:users, :external_email, false)
   -> 1057.0669s

Since changing NOT NULL shouldn't take more than maybe a second I suspect a lot of updates on the users table were preventing this statement from acquiring a lock briefly necessary to make the changes. It's possible an explicit use of LOCK users IN EXCLUSIVE MODE could solve it, but this also depends a lot on the rate of updates to this table.

When trying to debug https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12113 I noticed https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1762 is not part of %9.3 which is quite strange, as stable branches were created after merging that MR according to timeline posted on #release channel, as me and @grzesiek were closely following that.

Do we know what did happen? Did we create a stable branch from the master at that time? or did we create it from some past commit?

We badly need to apply this https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2163 to GitLab.com: specifically this patch: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2163.patch

Background processing had been disabled for around 30 minutes until we re-enabled it. It caught up on processing 17k jobs very fast.

mentioned in issue #33839 (closed)

mentioned in merge request !12268 (merged)

Post-deployment migrations couldn't be completed, here's the last few lines output for db:migrate:status on production.

52.177.192.107    up     20170524125940  Add source to ci pipeline
52.177.192.107    up     20170524161101  Add protected to ci variables
52.177.192.107    up     20170525132202  Create pipeline stages
52.177.192.107    up     20170525174156  Create feature tables
52.177.192.107    up     20170525174157  Create pipeline source pipeline
52.177.192.107    up     20170525174158  Add ci pipeline source pipeline indexes
52.177.192.107    up     20170525174159  Add ci pipeline source pipeline foreign key
52.177.192.107    up     20170526185602  Add stage id to ci builds
52.177.192.107    up     20170526185842  Migrate pipeline stages
52.177.192.107    up     20170526185858  Create index in pipeline stages
52.177.192.107   down    20170526185921  Migrate build stage reference
52.177.192.107   down    20170530111134  Ensure project mirror data
52.177.192.107    up     20170531180233  Add authorized keys enabled to application settings
52.177.192.107    up     20170531202042  Rename users ldap email to external email
52.177.192.107   down    20170531203055  Cleanup users ldap email rename
52.177.192.107    up     20170602003304  Add clone url prefix to geo node
52.177.192.107    up     20170603200744  Add email provider to users
52.177.192.107    up     20170606202615  Move appearance to system dir

I've created https://gitlab.com/gitlab-com/infrastructure/issues/2063 to figure out how we can read the old logs from staging that have been removed from the environment after we deployed RC3.

I couldn't check the actual time we deployed to staging as the task was not marked as done here... That would have helped a lot /cc @ClemMakesApps @kushalpandya

@kushalpandya Didn't you in Slack say that everything was "up"? Could you double check to make sure this is the case?

I couldn't check the actual time we deployed to staging as the task was not marked as done here... That would have helped a lot /cc

Sorry, I thought I did but apparently not but if you check slack, it was announced there @jameslopez

@yorickpeterse Yes, but that was after I ran migrations last time with MigrateBuildStageReference skipped.

@ClemMakesApps no worries! I've got lost on Slack as I wasn't sure if we deployed it twice. But I figured out in the end! :)

Gotcha @jameslopez. Glad you figured it out!

mentioned in issue gitlab-com/infrastructure#2066 (closed)

changed the description

marked the checklist item Cherry-pick merge requests labeled [Pick into Stable] for the current as completed

marked the checklist item Check that [EE packages are built], [CE packages are built] and appears on packages.gitlab.com: EE & CE as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc3 to staging as completed

marked the checklist item [Deploy] 9.3.0-rc3 to [staging.gitlab.com] as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc3 to production as completed

marked the checklist item [Deploy] 9.3.0-rc3 to GitLab.com as completed

marked the checklist item Tweet about the 9.3.0-rc3 release: as completed

changed the description

marked the checklist item Ensure https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2161 is merged (9-3-stable-ee-rc4 => 9-3-stable-ee) as completed

changed the description

marked the checklist item Cherry-pick merge requests labeled [Pick into Stable] for the current as completed

marked the checklist item Ensure https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12260 is merged (9-3-stable-rc4 => 9-3-stable) as completed

marked the checklist item Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.3.0-rc3-ee..9-3-stable-ee -- db/migrate db/post_migrate => as completed

marked the checklist item Merge CE 9-3-stable into EE 9-3-stable-ee following the [Merging a CE stable branch into its EE counterpart] guide as completed

marked the checklist item Sync CE, EE, and Omnibus to dev as completed

changed the description

marked the checklist item Ensure tests are green on [CE stable branch] as completed

changed the description

marked the checklist item In #releases: I'm going to tag 9.3.0-rc4 as completed

marked the checklist item Tag the 9.3.0-rc4 version using the [release task]: as completed

changed the description

Trying to add RC5 to the checklist but it's giving me an error.

I think I'm hitting the spam filter

@ClemMakesApps Indeed, I do see logs in the spam filter. Try again.

changed the description

Thanks @stanhu! I'm not sure but I suspect that the inline issue description editing might be blocking the recaptcha

changed the description

marked the checklist item [Deploy] 9.3.0-rc4 to [staging.gitlab.com] as completed

changed the description

marked the checklist item Check that [EE packages are built], [CE packages are built] and appears on packages.gitlab.com: EE & CE as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc4 to staging as completed

marked the checklist item [Deploy] 9.3.0-rc4 to [staging.gitlab.com] as incomplete

changed the description

marked the checklist item [Deploy] 9.3.0-rc4 to [staging.gitlab.com] as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc4 to production as completed

marked the checklist item [Deploy] 9.3.0-rc4 to GitLab.com as completed

marked the checklist item Tweet about the 9.3.0-rc4 release: as completed

marked the checklist item Cherry-pick merge requests labeled [Pick into Stable] for the current as completed

Finished cherry picking into RC5.

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12108 had a conflict when cherry picking, @MadLittleMods is working on resolving those conflicts in !12284 (merged)

[CE] 9-3-stable-rc5 into 9-3-stable: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12283
[EE] 9-3-stable-ee-rc5 into 9-3-stable-ee: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2173
[Omnibus] 9-3-stable-rc5 into 9-3-stable: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/1658

@kushalpandya hoping you get to deploy RC5 during IST timezone 😄

changed the description

marked the checklist item Ensure tests are green on [EE stable branch] as completed

changed the description

marked the checklist item Merge CE 9-3-stable into EE 9-3-stable-ee following the [Merging a CE stable branch into its EE counterpart] guide as completed

marked the checklist item Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.3.0-rc1-ee..9-3-stable-ee -- db/migrate db/post_migrate => as completed

marked the checklist item Sync CE, EE, and Omnibus to dev as completed

changed the description

changed the description

marked the checklist item Ensure tests are green on [CE stable branch] as completed

marked the checklist item Ensure tests are green on [EE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus CE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus EE stable branch] as completed

marked the checklist item In #releases: I'm going to tag 9.3.0-rc5 as completed

marked the checklist item Tag the 9.3.0-rc5 version using the [release task]: as completed

marked the checklist item Check that [EE packages are built], [CE packages are built] and appears on packages.gitlab.com: EE & CE as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc5 to staging as completed

marked the checklist item [Deploy] 9.3.0-rc5 to [staging.gitlab.com] as completed

changed the description

marked the checklist item In #releases: I'm going to tag 9.3.0-rc5 as incomplete

changed the description

marked the checklist item Cherry-pick merge requests labeled [Pick into Stable] for the current as completed

changed the description

changed the description

marked the checklist item Merge CE 9-3-stable into EE 9-3-stable-ee following the [Merging a CE stable branch into its EE counterpart] guide as completed

marked the checklist item Sync CE, EE, and Omnibus to dev as completed

marked the checklist item Ensure tests are green on [Omnibus EE stable branch] as completed

marked the checklist item Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.3.0-rc1-ee..9-3-stable-ee -- db/migrate db/post_migrate => as completed

changed the description

marked the checklist item In #releases: I'm going to tag 9.3.0-rc6 as completed

marked the checklist item Tag the 9.3.0-rc6 version using the [release task]: as completed

changed the description

changed the description

marked the checklist item [Deploy] 9.3.0-rc6 to [staging.gitlab.com] as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc6 to production as completed

marked the checklist item [Deploy] 9.3.0-rc6 to GitLab.com as completed

marked the checklist item Tweet about the 9.3.0-rc6 release: as completed

marked the checklist item Cherry-pick merge requests labeled [Pick into Stable] for the current as completed

changed the description

marked the checklist item Ensure tests are green on [CE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus CE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus EE stable branch] as completed

changed the description

marked the checklist item Merge CE 9-3-stable into EE 9-3-stable-ee following the [Merging a CE stable branch into its EE counterpart] guide as completed

marked the checklist item Sync CE, EE, and Omnibus to dev as completed

changed the description

marked the checklist item Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.3.0-rc1-ee..9-3-stable-ee -- db/migrate db/post_migrate => as completed

marked the checklist item In #releases: I'm going to tag 9.3.0-rc7 as completed

marked the checklist item Tag the 9.3.0-rc7 version using the [release task]: as completed

changed the description

marked the checklist item Check that [EE packages are built], [CE packages are built] and appears on packages.gitlab.com: EE & CE as completed

marked the checklist item In #production: I'm going to deploy 9.3.0-rc7 to staging as completed

marked the checklist item [Deploy] 9.3.0-rc7 to [staging.gitlab.com] as completed

changed the description

marked the checklist item In #production: I'm going to deploy 9.3.0-rc7 to production as completed

marked the checklist item [Deploy] 9.3.0-rc7 to GitLab.com as completed

changed the description

marked the checklist item Sync CE, EE, and Omnibus to dev as completed

marked the checklist item Ensure tests are green on [CE stable branch] as completed

marked the checklist item Ensure tests are green on [EE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus CE stable branch] as completed

marked the checklist item Ensure tests are green on [Omnibus EE stable branch] as completed

marked the checklist item In #releases: I'm going to tag 9.3.0 as completed

marked the checklist item Tag the 9.3.0 version using the [release task]: as completed

changed the description

marked the checklist item Check that [EE packages are built], [CE packages are built] and appears on packages.gitlab.com: EE / CE as completed

marked the checklist item In #production: I'm going to deploy 9.3.0 to production as completed

marked the checklist item Tweet about the deploy, at this point the deploy alert banner on GitLab.com should already be up. as completed

marked the checklist item Do the [deploy] of 9.3.0 to GitLab.com as completed

marked the checklist item Create the 9.3.0 version on https://version.gitlab.com as completed

changed the description

marked the checklist item Make sure following MRs are merged into master; as completed

mentioned in merge request gitlab-com/www-gitlab-com!6577 (merged)

closed