Mayra Cabrera requested to merge update-links-on-multi-patch-version-template into master Mar 08, 2023

What does this MR do and why?

Documentation for the patch release pressure and the broken stable branch process was updated on gitlab-org/release/docs!565 (merged). This commit updates the patch multi version template to use the new links.

Author Check-list

[-] Has documentation been updated?

Example

Click to expand

Releases 15.9.3, 15.8.5, 15.7.9

Preparation

Review if there are unreleased merge requests to be patched for each version. Adjust the versions if necessary.

Stable branches for projects under the GitLab Managed Versioning model are required to have a green pipeline to perform a patch release.

Verify pipelines on stable branches on GitLab are green:
Verify pipelines on the GitLab projects are green:

If a failure is found the resolution process differs between each project:

For GitLab project failures, follow the broken stable branch process.
For GitLab components, contact the maintainers and notify them about the failure.

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.

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 on the default branch due to security merges this mirror is expected to show as a broken and can be safely ignored.
```
/chatops run mirror status
```
Tag 15.9.3 and wait for the job to finish before tagging the next package:
```
/chatops run release tag 15.9.3
```
Tag 15.8.5 and wait for the job to finish before tagging the next package:
```
/chatops run release tag 15.8.5
```
Tag 15.7.9 and wait for the job to finish before tagging the next package:
```
/chatops run release tag 15.7.9
```
While waiting for packages to build, review and complete the blog post. => BLOG_POST_MR
- If the blog post failed to generate, it can be generated manually from the release-tools project with rake release:patch_release_blog_post.
Check the progress of the EE/CE packages:
- EE: 15.9.3+ee.0
- CE: 15.9.3+ce.0
- EE: 15.8.5+ee.0
- CE: 15.8.5+ce.0
- EE: 15.7.9+ee.0
- CE: 15.7.9+ce.0

Note this may take a while (around 80 minutes) and only the EE packages are required to continue with the 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 will only be performed for the current release version.

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:

/chatops run deploy 15.9.3-ee.0 release

Release

15.9.3

Publish the packages via ChatOps:
```
/chatops run publish 15.9.3
```
Verify that the chatops publish pipeline created by running the above command succeeded.
Verify the check-packages job completes successfully on the EE Pipeline
Verify the check-packages job completes successfully on the CE Pipeline
Verify that Docker images appear on hub.docker.com: EE / CE

15.8.5

Publish the packages via ChatOps:
```
/chatops run publish 15.8.5
```
Verify that the chatops publish pipeline created by running the above command succeeded.
Verify the check-packages job completes successfully on the EE Pipeline
Verify the check-packages job completes successfully on the CE Pipeline
Verify that Docker images appear on hub.docker.com: EE / CE

15.7.9

Publish the packages via ChatOps:
```
/chatops run publish 15.7.9
```
Verify that the chatops publish pipeline created by running the above command succeeded.
Verify the check-packages job completes successfully on the EE Pipeline
Verify the check-packages job completes successfully on the CE Pipeline
Verify that Docker images appear on hub.docker.com: EE / CE

Final steps

Merge the blog post.

Notify the patch release has been published (blog post link needs to be replaced with the actual link).

/chatops run notify ":mega: GitLab Patch Release: 15.9.3, 15.8.5, 15.7.9 has just been released: <blog post link>! Share this release blog post with your network to ensure broader visibility across our community."

Create the 15.9.3 version on version.gitlab.com.
Create the 15.8.5 version on version.gitlab.com.
Create the 15.7.9 version on version.gitlab.com.

Release Certification

The release certification process may apply to this release. cc @gitlab-com/gl-security/federal-application-security

Edited Mar 08, 2023 by Mayra Cabrera

Update links on the patch multi version template