This is an automated email from the ASF dual-hosted git repository.

wave pushed a commit to branch Nomenclature-updates
in repository https://gitbox.apache.org/repos/asf/tooling-docs.git


The following commit(s) were added to refs/heads/Nomenclature-updates by this 
push:
     new 03597d6  Lifecycle is Phases of Stages
03597d6 is described below

commit 03597d6dfccf51be22e5a3de533970b37e351b7e
Author: Dave Fisher <dave2w...@comcast.net>
AuthorDate: Sun Feb 2 13:16:30 2025 -0800

    Lifecycle is Phases of Stages
---
 apache-trusted-release/lifecycle.md | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/apache-trusted-release/lifecycle.md 
b/apache-trusted-release/lifecycle.md
index 6d8df4b..b0bdf37 100644
--- a/apache-trusted-release/lifecycle.md
+++ b/apache-trusted-release/lifecycle.md
@@ -1,5 +1,13 @@
 # Release Lifecycle
 
+A Release will go through a lifecycle of **stages** and **phases**.
+
+Stages include **Build**, **Candidate**, **Current**, and **Revoked**.
+The ATR does not manage build stage releases. It takes over on the transition 
from the build to the cnadidate stage.
+Stages control where on the **ATR** Website a release can be found.
+
+Phases are states or activities during a Release's life cycle.
+
 ```mermaid
 flowchart TD
     subgraph Apache Trusted Release
@@ -8,7 +16,7 @@ flowchart TD
     C@{ shape: docs, label: "Release Candidate" }
     A -->|automatically triggered| C
     B -->|manually triggered| C
-    subgraph Release Candidate
+    subgraph Release Candidate Stage
     D@{ shape: processes, label: "Evaluate Candidate" }
     C --> D
     DD@{ shape: process, label: "Sign Candidate" }
@@ -24,7 +32,7 @@ flowchart TD
     DD --> GG
     GG --> E
     end
-    subgraph Release
+    subgraph Current Release Stage
     JJ@{ shape: docs, label: "Release" }
     JJJ --> JJ
     G@{ shape: processes, label: "Distribute" }
@@ -49,10 +57,12 @@ flowchart TD
     end
 ```
 
-## Definitions
+## Phases
 
 **Announce CVEs**
-: At some moment after a release happens a project may announce CVEs that 
either impact or are solved by a release. The security team and PMC manage CVEs 
including announcements and publishing via cveprocess.apache.org The ATR will 
update SBOMs with new CVEs.
+: At some moment as or after a release happens a project may announce CVEs 
that either impact or are solved by a release. The security team and PMC manage 
CVEs including announcements and publishing via cveprocess.apache.org The ATR 
will update SBOMs with new CVEs.
+
+> Note where this is an explicit phase or not depends on integration 
discussions with the security team.
 
 **Announce Release**
 : Send a compliant announcement of the release. This template will include 
release metadata.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org
For additional commands, e-mail: dev-h...@tooling.apache.org

Reply via email to