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 0e47889 Remove overengineering
0e47889 is described below
commit 0e47889982b7f40acdedd6dfff392318eef52697
Author: Dave Fisher <[email protected]>
AuthorDate: Sun Feb 2 13:35:53 2025 -0800
Remove overengineering
---
apache-trusted-release/platform.md | 59 +++++++-------------------------------
1 file changed, 11 insertions(+), 48 deletions(-)
diff --git a/apache-trusted-release/platform.md
b/apache-trusted-release/platform.md
index 18c94d2..d953452 100644
--- a/apache-trusted-release/platform.md
+++ b/apache-trusted-release/platform.md
@@ -1,16 +1,13 @@
-# Platform Services
+# Platform Service
-1. Datastore: https://releases.apache.org
-2. Task Runner: https://artifacts.apache.org
-
-> Monitoring the service stack will indicate if the stack split is indicated.
Let's make sure that such a split is relatively quick.
+https://releases.apache.org
## Datastore
1. Release Storage. A large filesystem with folders for each release's files.
The release folder path is immutable.
2. Metadata Database. An sql database on the server with the metadata schema.
-### Web Service
+## Web Service
1. `asfquart` based asynchronous python web service.
2. Fronted by `httpd`.
@@ -18,7 +15,7 @@
4. Fronted by a CDN. The caching policies need to properly defined.
5. Avoid long running processes.
-### Release Metadata and Files
+### Release Stages
1. Current Releases
2. Candidate Releases
@@ -31,7 +28,7 @@
1. Collate Keys by Committer
2. Link Committer Keys to Project, Signed Releases
-### Release CVE Store
+### Release CVEs
1. CVE metadata
3. Affected releases
@@ -68,16 +65,14 @@ The co-ordinates make up the external path to objects. The
metadata database pro
- SBOMs - Special files stored in the release folder.
- CVEs - CVE metadata and release linkage.
-3. POST Actions - Transitions with a Task
- - Analyze
- - Vote Monitor
- - Distribute - Push to Package Repositories
- - Push / Pull with dist.apache.org
- - others?
+3. POST Phases - Transitions, Activities, and Communication
+ - Transition into Phase.
+ - Perform Phase activity.
+ - Optionally email phase status.
- See [Release Lifecycle](./lifecycle.md) for how Actions are chained
together to perform a Release.
+ See [Release Lifecycle](./lifecycle.md) for how phases are chained together
to perform a Release.
-4. POST Templated Release Emails
+4. POST Templated Emails
- Announcements
- Votes
- Status
@@ -110,36 +105,4 @@ The co-ordinates make up the external path to objects. The
metadata database pro
- Responsive with Header(Hamburger)/Content/Footer.
- Include Search in Header(Hamburger)
-## Task Runner
-
-1. Runner for processes taking more than a few seconds.
-2. Manages an array of concurrent tasks.
-3. Provides operational status.
-4. Monitor load to avoid saturation and find true limits.
-
-### Web Service
-
-1. `asfquart` based asynchronous python web service.
-2. Fronted by `httpd`.
-3. Limit web access to ATR Datastore, other Runners, and IRD.
-
-### Restful API
-
-See [Release Lifecycle](./lifecycle.md) for how Action Tasks are chained
together to perform tasks related to a Release.
-
-1. GET
- - Status
- - Task
-
-2. CRUD on
- - Task
-
-3. Task Types
- - Analyze
- - Test Distribution
- - Vote Monitor
- - Distribution
- - Monitor Manual Distribution
- - Push / Pull with dist.apache.org
- - others?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
