Merge "M4 status Groupbasedpolicy"

[docs.git] / docs / release-process / project-lifecycle.rst

diff --git a/docs/release-process/project-lifecycle.rst b/docs/release-process/project-lifecycle.rst
index 689f79fa2424544a2f47c1ea97dd3fe680706fed..2e6d6693e6d193921012dc008227af3c718c9046 100644 (file)
--- a/docs/release-process/project-lifecycle.rst
+++ b/docs/release-process/project-lifecycle.rst
@@ -21,28 +21,35 @@ progress to the following state.
   The recognized project is willing to participate, but its current codebase is
   not passing its own merge job, or the project artifacts are otherwise
   unavailable in Nexus.
-- **failing-distribution-check**
-  Merge job passes, but project distribution-check job is either not defined
-  or failing.
 - **not-in-autorelease**
-  Project distribution-check passes, but the project is not added to
-  autorelease (git submodule, maven module)
+  Project merge job passes, but the project is not added to
+  autorelease (git submodule, maven module, validate-autorelease job passes).
+- **failing-autorelease**
+  The project is added to autorelease (git submodule, maven module, validate-autorelease job passes),
+  but autorelease build fails when building project's artifact.
+  Temporary state, timing out into not-in-autorelease.
 - **repo-not-in-integration**
-  Project is added do autorelease, but integration/distribution:features-index
-  is not listing all its feature repositories.
+  Project is succesfully built within autorelease, but integration/distribution:features-index
+  is not listing all its public feature repositories.
 - **feature-not-in-integration**
-  Feature repositories are referenced, but some user-facing features are absent
-  from integration/distribution:features-test
+  Feature repositories are referenced, distribution-check job is passing,
+  but some user-facing features are absent from integration/distribution:features-test
+  (possibly because adding them does not pass distribution SingleFeatureTest).
+- **distribution-check-not-passing**
+  Features are in distribution, but distribution-check job is either not running,
+  or it is failing for any reason. Temporary state, timing out into feature-not-in-integration.
 - **feature-is-experimental**
-  All user-facing features are in features-test, but at least one corresponding
-  functiona CSIT jobs does not meet integration/test requirements.
-- **ready**
+  All user-facing features are in features-test, but at least one of the corresponding
+  functional CSIT jobs does not meet Integration/Test requirements.
+- **feature-is-not-stable**
+  Feature does meet Integration/Test requirements, but it does not meed all requirements for stable features.
+- **feature-is-stable**
 
 .. note::
 
    A project may change its state in both directions, this list is to make sure
-   a project is not left in an invalid state, for example present in
-   autorelease but without passing distribution-check job.
+   a project is not left in an invalid state, for example distribution referencing
+   feature repositories, but without passing distribution-check job.
 
 .. todo::
 
@@ -51,6 +58,4 @@ progress to the following state.
    - Mention other jobs involved in verification (verify, validate-autorelease, ... releng-check-poms).
    - Add back-references to this document (from integration/distribution, job definition templates, ...).
    - Do we need a special rules applicable at Release Review?
-   - By adding features to integration, distribution-check job may start failing on issues
-     that were not visible before. Document a workaround or create a specialized verify-like job.
    - Mention that some rules do not make sense for Integration/Distribution project, provide substitute rules.