Discourage release posts for code merged on the 17th
Why is this change being made?
Code merged on the 17th is not guaranteed to be part of a release, so release posts should probably not be merged for code merged on the 17th. Also, discouraging release posts based on last-minute code merges will help alleviate some of the urgency and stress centered on the 17th.
Related to this, Manage stage is now considering the 15th a soft cutoff date for code merge. Code merged after the 15th is assumed not to make the release.
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 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 relate to any part of the project other than updates to content and/or data files please make sure to ping(this requirement has been removed pending identification of a new DRI for the handbook)@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.