Automate creating patch release blog posts
Summary
Patch release issues contain the following TODO:
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
The template for patch releases is https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/templates/blog/patch_release_blog_template.html.md.erb.
We should investigate the possibility of automatically creating MRs containing all necessary details. This requires that we somehow tag MRs so we know which release they went into. This could be done by automatically generating "Picked into X.Y.Z" labels and using those, or by somehow parsing the notes from the preparation MRs (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24941). This also requires that MRs have the proper edition label (starter, core, etc) since the patch release contains sections for these editions.
Implementation
-
Generate the blog post MR when the /chatops run release prepare <version>
command is executed - gitlab-org/release-tools!1626 (merged). -
Create the patch blog MR when patch issue is created - gitlab-org/release-tools!1627 (merged). -
Add list of cherry-picked MRs to the blog post MR when /chatops run release merge <version>
is executed - gitlab-org/release-tools!1633 (merged).
Cleanup:
-
Update template location in docs if we copy template to release-tools - gitlab-com/www-gitlab-com!95067 (merged). -
Remove feature flag generate_patch_blog_post
(https://ops.gitlab.net/gitlab-org/release/tools/-/feature_flags/211/edit) once this is confirmed to work correctly - gitlab-org/release-tools!1676 (merged).
Remaining cleanup issues moved to #2216 (closed).
Refactor:
-
Move PatchIssue
andSecurityPatchIssue
intoPatchRelease
module - gitlab-org/release-tools!1636 (merged).
Items not automated as part of this issue
The blog post is still not merge-ready after this, since there are small changes that need to be done manually, like:
- Adding twitter username.
- Correcting the GitLab username.
- Adding the correct blog link for the major version that is being patched.
- Modifying the sentence about migrations if the patch has new migrations.