Blog Post: We're Combining Patch & Security releases
Triage (REQUIRED)
Please note that there is a different process for when you want to announce something via the blog. Please see announcement requests in the handbook and open an announcement request issue instead of a blog post issue.
Proposal
As part of Automate combining bug fixes and security fixes... (gitlab-com/gl-infra&1073 - closed) we are modifying some of the processes through which we release and communicate about changes to GitLab releases. This blog post is intended to walk customers through the changes and the reasoning and also give them a high level view of what is/isn't changing
Checklist
-
Does this align with a time-sensitive release, campaign or announcement? Please add link to pertinent info such as eBook landing page -
If wide-spread customer impacting or sensitive, mention @lboughner
to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue -
If the post is about one of GitLab's Technology Partners, including integration partners, mention @pattycheung
and@nbadiey
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts -
If the post is about one of GitLab's customers, mention @nicolecsmith
, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts -
Indicate if this post requires additional approval from internal or external parties before publishing (please tag needed sign off DRIs as necessary) -
Please upload any images to the MR before tagging the editorial team.
Questions?
-
Please tag @Sgittlen with any questions/concerns/confusion.
Edited by Sam Wiskow