From bb24d526f88e08f355a2cc41b53feeaf75f16348 Mon Sep 17 00:00:00 2001 From: Filippo Valsorda Date: Mon, 23 Apr 2018 14:16:27 -0400 Subject: [PATCH] Updated MinorReleases (markdown) --- MinorReleases.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/MinorReleases.md b/MinorReleases.md index 36e3e828..c2ecc341 100644 --- a/MinorReleases.md +++ b/MinorReleases.md @@ -12,7 +12,9 @@ The fix is developed for the main issue, which is closed when the fix is merged 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**. Release managers 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 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. +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. Gerrit is configured to only allow release managers to submit to release branches, but the code review process is otherwise the usual. + +The cherry-pick CL must include a message prefix like `[release-branch.go1.10]`, and update the "Fixes" line to the child issue. 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.