Release 12.7.1 -> 12.7.2
Preparation
-
Preparation MR's should already be created
- GitLab: gitlab-org/gitlab!23551 (merged)
- Omnibus: gitlab-org/omnibus-gitlab!3875 (merged)
-
[-] Ensure any backports targeting 12.7.1 are merged to their stable counter part
- [-] EE Backports
- [-] Omnibus EE
-
Perform automated merging into the preparation branches: # In Slack /chatops run release merge 12.7.1
-
Merge the preparation branches -
Check the following list of critical issues/MRs which are to be included in
12.7.1
.-
gitlab-org/gitlab!23428 (merged) ~P1 / ~S1 - MR targeting stable branch: gitlab-org/gitlab!23561 (merged) - [-] gitlab-org/gitlab!23264 (merged) ~P1 / ~S2 - Not necessary, already included on %12.7
-
gitlab-org/omnibus-gitlab!3878 (merged) -
gitlab-org/gitlab!23621 (merged) ~P1 / ~S2 - gitlab-org/gitlab!23639 (merged)
-
-
List of non-critical MR that had conflicts:
- [-] gitlab-org/gitlab!19962 (merged) - Not necessary, already included on %12.7
-
gitlab-org/gitlab!23446 (merged) - gitlab-org/gitlab!23591 (merged)
-
Ensure builds are green on Omnibus
Packaging
-
Check if mirroring synced stable branches to dev. If the output is ✅ for every repo, we can proceed to tag.# In Slack /chatops run mirror status
-
Tag 12.7.1
:# In Slack: /chatops run release tag 12.7.1
-
[-] While waiting for packages to build, now is a good time to prepare the blog post. Look at previous MRs for examples. => BLOG_POST_MR
-
[-] Check progress of EE packages build and CE packages build.
- This might take a while (around 80 min).
- We only need the EE packages to finish to continue with next steps.
12.7.2
Context
12.7.1
was canceled given it included a feature - gitlab-org/gitlab!22744 (comment 276580016)
12.7.2
needs to be started without that feature
Prep
-
Revert gitlab-org/gitlab!22744 (merged) from 12-7-stable-ee
branch - gitlab-org/gitlab!23691 (merged) -
Wait until pipelines are green on stable branches - https://gitlab.com/gitlab-org/gitlab/commits/12-7-stable-ee -
Ensure builds are green on Omnibus
Packaging
-
Check if mirroring synced stable branches to dev. If the output is ✅ for every repo, we can proceed to tag.# In Slack /chatops run mirror status
-
Tag 12.7.2
:# In Slack: /chatops run release tag 12.7.2
-
While waiting for packages to build, now is a good time to prepare the blog post. Look at previous MRs for examples. => gitlab-com/www-gitlab-com!39345 (merged) -
Check progress of EE packages build and CE packages build. - This might take a while (around 80 min).
- We only need the EE packages to finish to continue with next steps.
Deploy
For patch releases, the only available environment for deploys is pre.gitlab.com
. All GitLab Inc. team members can login to that installation using their email address (through google oauth).
pre.gitlab.com
Deployments to pre.gitlab.com are performed automatically. If you need to manually run a deployment, you can do so as follows:
# In Slack:
/chatops run deploy 12.7.2-ee.0 --pre
QA
The QA task issue needs to be manually generated, you can do so as follows:
# In Slack, replacing LAST_DEPLOYED_VERSION with the appropriate value:
/chatops run release qa vLAST_DEPLOYED_VERSION v12.7.2
QA issue: https://gitlab.com/gitlab-org/release/tasks/issues/1185
Release
-
Publish the packages via ChatOps: # In Slack: /chatops run publish 12.7.2
-
Create the 12.7.2
version on version.gitlab.com -
Deploy the blog post -
In the #content-updates
channel, share a link to the blog post::tada: GitLab 12.7.2 has been released: https://about.gitlab.com/releases/2020/01/24/gitlab-12-7-2-released/
References
gitlab.com
- https://gitlab.com/gitlab-org/gitlab-foss/commits/12-7-stable
- https://gitlab.com/gitlab-org/gitlab/commits/12-7-stable-ee
- https://gitlab.com/gitlab-org/omnibus-gitlab/commits/12-7-stable