Release 15.3.3
Preparation
- Preparation MR's should already be created
-
Ensure 15-3-stable-ee
GitLab branch is green. -
Perform automated merging into the preparation branches: # In Slack /chatops run release merge 15.3.3
-
Wait for confirmation from Release Managers that no security release will be required for https://gitlab.com/gitlab-sirt/incident_2562/-/issues/1 - => Update August 31st - No security release will be required for the SIRT incident https://gitlab.com/gitlab-sirt/incident_2562/-/issues/1#note_1084564465
-
Run /chatops run release merge 15.3.3
again to include gitlab-org/gitlab!95974 (merged) - Merge the preparation merge requests
-
gitlab-org/gitlab
gitlab-org/gitlab!96654 (merged) -
gitlab-org/omnibus-gitlab
- gitlab-org/omnibus-gitlab!6304 (merged) -
gitlab-org/build/CNG
gitlab-org/build/CNG!1118 (closed)
-
-
Ensure any backports targeting 15.3.3 are merged to their stable counter part
-
Process gitlab-org/gitlab!96556 (merged) -
Ensure it's approved by a maintainer. -
Rebase the MR against the stable branch. This can be done with the /rebase
quick action -
Once the pipeline is green, merge it.
-
-
GitLab Backports -
Omnibus -
CNG -
Gitaly
-
- Check the following list of critical issues/MRs which are to be included in
15.3.3
.-
REFERENCE_TO_MR_TO_PICK
-
- [-] Ensure that any post-deploy migrations in the stable branch have been executed on GitLab.com by executing the post-deploy migration pipeline:
/chatops run post_deploy_migrations execute
.- => Mayra: Not required since no post-migrations were included in gitlab-org/gitlab!96654 (merged)
-
Ensure builds are green on Omnibus
Backport request
If this patch release is part of a backport request, we will not be able to deploy the package to our release instance. Now is the time to kick off QA. Refer to the backport QA testing documentation to complete this task:
- [-] QA is complete, and sign-off by the current QA on-call is noted as a comment on this issue. (not required for this patch release)
Packaging
-
Check if mirroring synced stable branches to dev. If the output is ✅ for every repo, we can proceed to tag. Note. If GitLab Canonical to Security mirroring has diverged due to security merges this mirror is expected to show as a broken and can be safely ignored.# In Slack /chatops run mirror status
-
Tag 15.3.3
:# In Slack: /chatops run release tag 15.3.3
-
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!110528 (merged) -
Check progress of EE packages build and CE packages build. /chatops run release status 15.3.3
- 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 release.gitlab.net
. All GitLab Inc. team members can login to that installation using their email address (through google oauth).
Deployment to release.gitlab.net is not required if the patch release is not for the latest completed monthly release version. This is because release.gitlab.net will be on the latest monthly release, and deploying a patch of an older version will require rolling back release.gitlab.net.
release.gitlab.net
Deployments to release.gitlab.net are performed automatically.
Instructions to manually deploy if required.
If you need to manually run a deployment, you can do so as follows:
# In Slack:
/chatops run deploy 15.3.3-ee.0 release
Release
-
Publish the packages via ChatOps: # In Slack: /chatops run publish 15.3.3
-
Verify that EE packages appear on packages.gitlab.com
: EE -
Verify that CE packages appear on packages.gitlab.com
: CE
Package Counts
Inside of the omnibus-gitlab pipelines, the Package-and-image-release
stage contain many jobs. For all jobs that are part of an Operating System Package, count each of them one time, with the exception of CentOS 7, count this one 3 times.
For example, for 14.9.X-ee:
- AmazonLinux-2-arm64-release
- AmazonLinux-2-release
- CentOS-7-release
- CentOS-8-arm64-release
- CentOS-8-release
- Debian-9-release
- Debian-10-arm-release
- Debian-10-release
- Debian-11-arm-release
- Debian-11-release
- OpenSUSE-15.3-arm64-release
- OpenSUSE-15.3-release
- SLES-12.5-release
- SLES-15.2-release
- Ubuntu-18.04-release
- Ubuntu-20.04-arm-release
- Ubuntu-20.04-release
The above would produce 19 total packages.
Points of importance:
- The amount and type of these jobs changes over time, therefore the number of packages created may change with each release
- Reach out to the Distribution team for any questions related to needing to confirm packages
- CE normally has fewer packages
-
Verify that Docker images appear on hub.docker.com
: EE / CE -
Deploy the blog post -
Create the 15.3.3
version on version.gitlab.com
References
gitlab.com
- https://gitlab.com/gitlab-org/gitlab-foss/commits/15-3-stable
- https://gitlab.com/gitlab-org/gitlab/commits/15-3-stable-ee
- https://gitlab.com/gitlab-org/omnibus-gitlab/commits/15-3-stable
dev.gitlab.org
- https://dev.gitlab.org/gitlab/gitlabhq/commits/15-3-stable
- https://dev.gitlab.org/gitlab/gitlab-ee/commits/15-3-stable-ee
- https://dev.gitlab.org/gitlab/omnibus-gitlab/commits/15-3-stable
Release Certification
The release certification process may apply to this release. cc @gitlab-com/gl-security/federal-application-security