Release 12.1.13
General guidelines
- Be sure to follow the Security Releases general information and Security Releases as Release Manager.
- Always work on https://dev.gitlab.org/. Do not push anything to https://gitlab.com
- Deployment tasks (staging, production canary VMs, and production) should be done only if the patch is for the latest version. Feel free to delete those sections if they don't apply.
Preparation
-
Merge security merge requests using chatops: # In Slack: /chatops run release merge --security
-
If any merge requests could not be merged, investigate what needs to be done to resolve this issues. Do not proceed unless it has been determined safe to do so. -
Merge ce/12-1-stable
intoee/12-1-stable-ee
Packaging
-
Push omnibus-gitlab/12-1-stable
todev
only:git push dev 12-1-stable
-
Ping the Security Engineers so they can get started with the blog post. The blog post should also be done on https://dev.gitlab.org/ in a private snippet: BLOG_POST_SNIPPET -
Ensure tests are green on CE -
Ensure tests are green on EE -
Tag 12.1.13
:# In Slack: /chatops run release tag --security 12.1.13
-
Check that EE packages are built and CE packages are built
Deploy
Deploy to Pre for QA testing
-
Deploy 12.1.13
to preprod# In Slack: /chatops run deploy 12.1.13-ee.0 --pre
QA
The QA task issue is manually generated, you can do so as follows:
# In Slack, replacing LAST_DEPLOYED_VERSION with the appropriate value:
/chatops run release qa --security vLAST_DEPLOYED_VERSION v12.1.13
-
Notify @appsec-team that packages are ready for QA # In Slack @appsec-team - Security release packages are available for QA.
-
Wait for the QA tasks deadline to pass.
Release
-
This section should be done in coordination with the Security team, so make sure to confirm with them before proceeding # In Slack @appsec-team - We are ready to publish the security release packages for 12.1.13, please let us know if the blog post is ready.
-
Publish the packages via ChatOps: # In Slack: /chatops run publish 12.1.13
-
Create the 12.1.13
version on version.gitlab.com. Be sure to mark it as a security release. -
Push ce/12-1-stable
to all remotes -
Push ee/12-1-stable-ee
to all remotes -
Push omnibus/12-1-stable
to all remotes -
Push CE, EE and omnibus tags to all remotes -
In the #content-updates
channel, share a link to the blog post::tada: GitLab 12.1.13 has been released: BLOG_POST_URL
-
Merge security MRs targeting master: # In Slack: /chatops run release merge --security --master
-
Push ce/master
to all remotes -
Push ee/master
to all remotes -
Push omnibus/master
to all remotes
For references: