2018-11-09: 11.5.0-rc5 exception request for gitlab-org/gitlab-ce!22919
- Merge request to be considered for picking: gitlab-org/gitlab-ce!22919
Why it needs to be picked
This is a foundational need for the Framework Delivery team's plans to automatically revert merges that break master
, among other plans.
The benefit is that it will unblock work for the team going forward.
The urgency is that we're trying to rapidly iterate on the release process, and delaying it another month would slow that down considerably.
Possible alternatives would create bigger risks than approving the exception request would.
Potential negative impact of picking
There should be no noticeable impact, as this is adding a new API endpoint. Worse case scenario we can block the endpoint at the HAproxy level on gitlab.com.
Release manager sign-off
-
Release manager
Sign-off for RC (delete this section if patch release)
Upon initial approval, the release manager will then ping and assign the following roles:
-
Engineering Manager -
Director of Engineering department (if different from Engineering Manager) -
Engineering Manager, Quality
If you are the last person to provide initial approval, assign this issue to the VPE for their approval:
-
VPE
After approval
Check that the following is accurate before closing this issue:
-
MERGE_REQUEST_REFERENCE has the correct milestone and label set so that the release managers will pick it. -
MERGE_REQUEST_REFERENCE has a comment with a link to this issue: - Exception approved in ISSUE_LINK