Skip to content

Add link from handbook to feature branch RP flow, post 18th

Mike Jang requested to merge mjang-link-to-howto-MR-from-release-branch into master

Why is this change being made?

Subject: Release Post flow

The current plan for 13.1 is to ask people who want to submit RP items, after the 18th at 8am PT, to create an MR targeted at the feature (release-X-Y) branch (instead of master).

This works with the following new section in our docs, https://docs.gitlab.com/ee/topics/git/feature_branch_development.html, which explicitly cites GitLab's release posts as the use case.

This would allow the Release Post Manager (and others) the opportunity to explicitly approve (or not) a new item, submitted after the noted time, for the upcoming release post.

I've also fixed an error with the TW Lead review of the MVP entry.

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
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • 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 relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack

Edited by Mike Jang

Merge request reports