Service release code freeze checkpoint

Change-Id: I6f7909ae075292d54b08f24aec0455e81541ba02
Signed-off-by: Daniel de la Rosa <ddelarosa@luminanetworks.com>

diff --git a/docs/release-process/managed-release.rst b/docs/release-process/managed-release.rst
index 458c7bc6b3acfa32cfd9ca9e22e040c1f914ac73..920c26084de0ce2fedb0ce3ffb626b7063e59e10 100644 (file)
--- a/docs/release-process/managed-release.rst
+++ b/docs/release-process/managed-release.rst
@@ -458,6 +458,27 @@ The remaining artifacts will be automatically scraped:
   * Number of reviews per-reviewer.
 * Grievances raised against the project since the start of the release.
 
+
+Service Release Code Freeze
+-------------------------------------------------------------
+
+There will be an additional checkpoint for Service Releases, where code will
+freeze one week before the schedule release. Here are more details:
+
+* After code-freeze, the specific branch will be locked down, just like with
+  a major release.
+
+* Once the branch is locked, only fixes for blocker bugs will be allowed
+  as long as they are approved by TSC and Release PM.
+
+* Bugs or Regression discovered during RC test will also be considered by
+  Release PM.
+
+* Release PM will track and allow those fixes that have not been reviewed
+  or merged because of project low activity or lack of committers. The
+  deadline to communicate the list of patches waiting review for a
+  particular Service Release is the code freeze date.
+
 Managed Release Integrated Release Process
 ------------------------------------------