From c25733d9f995f9b63e09ac37f5e5d787320ff7d1 Mon Sep 17 00:00:00 2001 From: Filippo Valsorda Date: Thu, 19 Apr 2018 14:46:53 -0400 Subject: [PATCH] Updated MinorReleases (markdown) --- MinorReleases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MinorReleases.md b/MinorReleases.md index dd886ba5..a63e7009 100644 --- a/MinorReleases.md +++ b/MinorReleases.md @@ -6,7 +6,7 @@ The fix is developed for the main issue, which is closed when it’s merged to t The child issue is assigned to the minor release milestone, is labeled **CherryPickCandidate**, and its candidacy is discussed there. Once it’s approved it transitions to **CherryPickApproved**. OSP team members and/or code owners approve cherry-picks via an informal process. -The original change author creates a cherry-pick change immediately against the release branch, and gets it merged with the approval of the OSP as soon as it's ready. This closes the child issue. Gerrit is configured to restrict submissions to the release branches to CLs with a +2 from a member of the OSP. +The original change author creates a cherry-pick change immediately against the release branch, and gets it merged as soon as it's ready. This closes the child issue. (The change should include a "Fixes" line for the child issue.) Gerrit is configured to only allow release managers to submit to release branches, but the code review process is otherwise the usual. At release time, any open backport issue which is not release-blocker is pushed to the next minor release milestone, and a minor release is minted with the already merged changes.