From e281bf21af14334ec67a0b25f35238f39a31b4a7 Mon Sep 17 00:00:00 2001 From: Filippo Valsorda Date: Mon, 23 Apr 2018 14:36:05 -0400 Subject: [PATCH] Updated MinorReleases (markdown) --- MinorReleases.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/MinorReleases.md b/MinorReleases.md index b7ae17c5..f682628a 100644 --- a/MinorReleases.md +++ b/MinorReleases.md @@ -12,11 +12,19 @@ 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 should immediately create and mail a cherry-pick change against the release branch, which will be merged as soon as it's ready, closing 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 should immediately create and mail a cherry-pick change against the release branch, which will be merged as soon as it's ready, closing 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. + +## Making cherry-pick CLs + +Once the main fix has been submitted to master, take note of its commit hash. + +TODO 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. +Gerrit is configured to only allow release managers to submit to release branches, but the code review process is otherwise the usual. ## Security releases