Skip to content

Update trusted-releases.md minor text changes #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dave2wave merged 1 commit into from
Aug 30, 2026
+3 −3
Merged

Update trusted-releases.md minor text changes #99

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/pages/trusted-releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ The main project for the Tooling Initiative is the Apache Trusted Releases (ATR)

## Websites

- https://releases.apache.org - this is the ATR UX which is dynamic requiring ASF login credentials.
- https://releases.apache.org - this is the ATR UX which is dynamic, requiring ASF login credentials.
- https://release-catalog.apache.org - this is the full ASF release catalog in a static website hosted by httpd.

## Repositories
Expand Down Expand Up @@ -69,7 +69,7 @@ There are many different project settings. These are categorized according to th
2. Metadata - the project name, description, and other urls. Some of these are required.
3. Security - security emails and threat model urls.
4. Lifecycle - how the project handles versioning. `semver`, `calver`, or `simple`.
5. Trusted Publishing - what GitHub repositories, branch, and workflows to trust.
5. Trusted Publishing - what GitHub repositories, branches, and workflows to trust.
6. Compose - license checking and other composition settings.
7. Vote - voting options and email templates.
8. Finish - distribution subdirectory and announcement email templates.
Expand All @@ -79,7 +79,7 @@ You can review these in the ATR website and then export a yaml fragment to save
### Release Manager

Each Release Manager should manage their access tokens and keys. At a minimum new Release Managers will need to save their OpenPGP public key.
Depending on the method chosen to upload your release candidate artifacts PATs, JWTs, or SSH keys may be required.
Depending on the method chosen to upload your release candidate artifacts, PATs, JWTs, or SSH keys may be required.

## Release Candidate Phases

Expand Down