Merge "Adjust code after branching silicon"

[docs.git] / docs / release-process / managed-release.rst

diff --git a/docs/release-process/managed-release.rst b/docs/release-process/managed-release.rst
index 2dfa73fa410e50ef8d439595b697e3a5ac86102a..084cf49e50dc0bdb5d11212b18fa8c938c6e2fd8 100644 (file)
--- a/docs/release-process/managed-release.rst
+++ b/docs/release-process/managed-release.rst
@@ -96,8 +96,15 @@ to follow a different release process.
 For implementation reasons, the projects that are able to release independently
 must depend only on other projects that release independently. Therefore the
 Release Integrated Projects will form a tree starting from odlparent. Currently
-odlparent and yangtools are the only Release Integrated Projects, but others
-may join them in the future.
+the following projects are Release Integrated:
+
+* aaa
+* controller
+* infrautils
+* mdsal
+* netconf
+* odlparent
+* yangtools
 
 Requirements for Managed Projects
 ---------------------------------
@@ -458,6 +465,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
 ------------------------------------------
 
@@ -699,5 +727,5 @@ Vocabulary Reference
   Simultaneous Release. These projects are consumed by Snapshot Integrated
   Projects based on release version numbers, not snapshot versions.
 
-.. _Committer Removal Process: https://wiki.opendaylight.org/view/TSC:Main#Committer_Removal_Process
+.. _Committer Removal Process: https://wiki-archive.opendaylight.org/view/TSC:Procedures_and_Processes#Committer_Removal_Process
 .. _Weather Page: https://jira.opendaylight.org/browse/TSC-132?jql=Project%20%3D%20TSC%20AND%20Type%20%3D%20%22Weather%20Item%22%20