From 847452df92f9349db876943939a4bfd665f2a029 Mon Sep 17 00:00:00 2001 From: Andrew Gerrand Date: Thu, 25 Jun 2015 22:30:32 +1000 Subject: [PATCH] Updated Go Release Cycle (markdown) --- Go-Release-Cycle.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Go-Release-Cycle.md b/Go-Release-Cycle.md index c12593f4..e7e93b88 100644 --- a/Go-Release-Cycle.md +++ b/Go-Release-Cycle.md @@ -5,7 +5,9 @@ The current cycle is to make a major release every six months. * Three months of general development. * Three months of release testing, known as the "feature freeze". -During the freeze, only bug fixes and doc updates are accepted. New work may be permitted by the core team, but only in truly exceptional cases and only if the work was proposed and approved before the cutoff. +During the freeze, only bug fixes and doc updates are accepted. Changes that were mailed before the freeze can be submitted if they are reviewed after the freeze. + +On occasion new work may be done during the freeze, but only in exceptional circumstances and typically only if the work was proposed and approved before the cutoff. Such changes should be low risk. The releases fall on Feb 1 and Aug 1, so the schedule is: @@ -18,4 +20,4 @@ One or more release candidates are cut during the freeze for the community to te ## Minor releases -Minor releases (e.g., 1.5.x) may be issued in the interim to address critical issues. Unlike major releases, only the fixes for the issues that motivated the release will be cherry-picked. \ No newline at end of file +Minor releases (1.x.y) may be issued between major releases to address critical issues (typically stability or security issues). Only fixes for which there is no workaround (usually the issues that motivated the release) will be cherry-picked for minor releases. \ No newline at end of file