Mention odlparent in project lifecycle

Odlparent is not part of autorelease,
so the current lifecycle states do not fit it much.

For now, only a note added, to be addressed later.

Change-Id: I6367ec0cbad3cf72ee179144036a72316927b237
Signed-off-by: Vratko Polak <vrpolak@cisco.com>

diff --git a/docs/release-process/project-lifecycle.rst b/docs/release-process/project-lifecycle.rst
index 2e6d6693e6d193921012dc008227af3c718c9046..9b85345cac7ea98aad05ad6041f852eede95ddb7 100644 (file)
--- a/docs/release-process/project-lifecycle.rst
+++ b/docs/release-process/project-lifecycle.rst
@@ -5,8 +5,8 @@ Project lifecycle
 This page documents the current rules to follow when adding and removing
 a particular project to Simultaneous Release (SR).
 
-List of states
-==============
+List of states for projects in autorelease
+==========================================
 
 The state names are short negative phrases describing what is missing to
 progress to the following state.
@@ -51,6 +51,12 @@ progress to the following state.
    a project is not left in an invalid state, for example distribution referencing
    feature repositories, but without passing distribution-check job.
 
+.. note::
+
+   Projects can participate in Simultaneous Release even if they are not included in autorelease.
+   Nitrogen example: Odlparent.
+   FIXME: Clarify states for such projects (per version, if they released multiple times within the same cycle).
+
 .. todo::
 
    - Add links to documents concerning project lifecycle from TSC point of view.