Skip to content

[Automation] Create release:start task

Brian Rhea requested to merge create-release-start-task into master

Why is this change being made?

Based on feedback from @nagyv-gitlab on #12766 (closed), this MR will automate the manual process of Creating the Release Post MR and additional branches, MRs, and files.

After Creating the Release Post branch and required directories/files with bundle exec rake "release:monthly", the RPM can run bundle exec rake "release:start" and task will perform all of the available actions below which must currently be done manually.

  • create an MR with the release post template

  • The source branch must be release-X-Y and the target branch master

  • Set the title to Draft: Release post - GitLab X.Y. Prefix the title with Draft:.

  • find and replace all the details described in the header of the template

  • create new branch: release-X-Y-bugs

  • create new branch: release-X-Y-performance-improvements

  • create new branch: release-X-Y-usability-improvements

  • create MR: Draft: release-X-Y-bugs (Release-Post-Bug-Usability-PerformanceImprovement-Block template)

  • create MR: Draft: release-X-Y-performance-improvements (Release-Post-Bug-Usability-PerformanceImprovement-Block template)

  • create MR: Draft: release-X-Y-usability-improvements (Release-Post-Bug-Usability-PerformanceImprovement-Block template)

  • Add the appropriate milestone to the above MRs

  • Confirm that Delete source branch when merge request is accepted is selected

  • Confirm they have the following labels: release post, release post item, Technical Writing

  • In each MR, replace the @mentions with the actual task owner names.

  • On the release-X-Y-bugs branch, add a new file to the data/release_posts/unreleased/ folder called bugs.yml and populate it with the content of bugs.yml

  • On the release-X-Y-usability-improvements branch, add a new file to the data/release_posts/unreleased/ folder called release-post-ux-improvements.yml and populate it with the content of release-post-ux-improvements.yml

  • On the release-X-Y-performance-improvements branch, add a new file to the data/release_posts/unreleased/ folder called performance_improvements.yml and populate it with the content of performance_improvements.yml

  • create an MVP issue based on !95272 (merged)

  • create a retrospective issue using https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/.gitlab/issue_templates/Release-Post-Retrospective.md

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Brian Rhea

Merge request reports