Skip to content

Cottage14 patch atr pages related to ATR #302

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

Open
cottage14 wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Cottage14 patch atr pages related to ATR #302

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f60450b
Create atr.md
cottage14 Aug 10, 2026
a14b74d
Update release-publishing.md added notes about ATR
cottage14 Aug 10, 2026
fd52e13
Update release-download-pages.md added note about ATR
cottage14 Aug 10, 2026
1654104
Update release-publishing.md added notes about ATR
cottage14 Aug 10, 2026
acc2ec3
Update release-integrity-primer.md added note about ATR
cottage14 Aug 10, 2026
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
13 changes: 13 additions & 0 deletions content/pages/atr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
Title: Apache Trusted Releases
license: https://www.apache.org/licenses/LICENSE-2.0

# Apache Trusted Releases

The Apache Trusted Releases (ATR) platform performs two key functions:

- it simplifies the process of preparing and approving a PMC's release of code
- it strengthens security around the release process so that both the project releasing the code and the users downloading it can be confident that the package contains only what it should

In August 2026, ATR is moving into **beta testing**. Its documentation during this period is available at <a href="https://release-test.apache.org/docs/introduction-to-atr" target="_blank">release-test.apache.org/docs/introduction-to-atr</a>.

When ATR is in general availability, its documentation will be at <a href="https://releases.apache.org/docs/introduction-to-atr" target="_blank">releases.apache.org/docs/introduction-to-atr</a>.

@dave2wave dave2wave Aug 11, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once ATR beta is fully functional then the documentation will be available at ...

6 changes: 4 additions & 2 deletions content/pages/release-download-pages.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,14 @@ license: https://www.apache.org/licenses/LICENSE-2.0

Your project's release download page is where people can download your product's latest release(s). This page describes how a release manager can put such a page together.

**Note**: Projects using the **Apache Trusted Releases (ATR)** platform should consult its [documentation](atr.html), which in part supersedes this information.

@dave2wave dave2wave Aug 11, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ATR does not remove the requirement to create download pages. What it does is handle the svn dist work for the Release Manager.


Review

- the policy on [release distribution](release-distribution.html) if you are unsure of the best way to use the project download page
- guidelines on [signing releases](release-signing.html)

## Contents ##
## Contents

<ul>
<li><a href="#links">Download links</a></li>
Expand Down Expand Up @@ -42,7 +44,7 @@ Your Apache project's download page:

<h3 id="current-and-older-releases">Current and older releases<a class="headerlink" href="#current-and-older-releases" title="Permanent link">&para;</a></h3>

Do **not** keep software distributions on your project's website. Move them to one of the two software distribution sites:
Do **not** keep software distributions on your project's website. Move them to one of these two sites:

- **Current public releases** appear on `downloads.apache.org/`. Place current, official releases that the PMC has approved for end-users on the main public release site. Make all changes at <a href="https://dist.apache.org/repos/dist/release/" target="_blank">`https://dist.apache.org/repos/dist/release/`</a>.

Expand Down
3 changes: 3 additions & 0 deletions content/pages/release-integrity-primer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
title: Handling Release Artifact Integrity Errors at the ASF
license: https://www.apache.org/licenses/LICENSE-2.0

## Release Integrity Primer

**Note**: Projects using the **Apache Trusted Releases (ATR)** platform should consult its [documentation](atr.html), which in part supersedes this information.

This page will help you resolve [release distribution policy](https://infra.apache.org/release-distribution) errors that our [Download Integrity Checker](https://github.com/apache/infrastructure-download-integrity-checker) discovers.
Each reported error has an accompanying error code (`CHKxx`). The code will help you resolve issues by using the matrix below:
Expand Down
10 changes: 8 additions & 2 deletions content/pages/release-publishing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,12 @@
Title: Release Creation Process
license: https://www.apache.org/licenses/LICENSE-2.0

These best practices help guide a PMC through the steps to create and publish an Apache software product release. It complements the formal <a href="https://www.apache.org/legal/release-policy.html" target="_blank">Apache Release Policy</a>, defining what must be in a software release, and [Release Distribution Policy](release-distribution.html).
These best practices help guide a PMC through the steps to create and publish an Apache software product release. They complement the formal <a href="https://www.apache.org/legal/release-policy.html" target="_blank">Apache Release Policy</a>, defining what must be in a software release, and [Release Distribution Policy](release-distribution.html).

Every Apache Software Foundation project software release must meet requirements for content, process, and publication. These requirements ensure that Apache contributors and users benefit from appropriate legal protection the ASF provides, and reflect the Foundation's goals of open, collaborative software development.

**Note**: Projects using the **Apache Trusted Releases (ATR)** platform should consult its [documentation](atr.html), which in part supersedes this information.

## Contents ##

- <a href="#definition">An Apache release</a>
Expand Down Expand Up @@ -41,7 +43,9 @@ By default, only PMC members can publish release artifacts to https://dist.apach

Allowing Committers to publish release artifacts requires project consensus, so include a link to an email thread with that consensus.

***Release managers do the mechanical work; but the PMC in general, and the PMC chair in particular (as an officer of the Foundation), remains responsible for compliance with ASF requirements.***
**Note**: Any PMC member of a project using the **ATR** platform can assign a **specific Committer** to the role of release manager, rather than giving blanket permission to all Committers of the PMC. To do this, open a Jira ticket for ATR with the details of your request.

@dave2wave dave2wave Aug 11, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, not a JIRA issue. This can be handled by a PMC member in ATR.


***Release managers do the mechanical work; but the PMC in general, and the PMC chair in particular (as an officer of the Foundation), remain responsible for compliance with ASF requirements.***

<h2 id="valid">A valid release package<a class="headerlink" href="#valid" title="Permanent link">&para;</a></h2>

Expand Down Expand Up @@ -134,3 +138,5 @@ As a rule of thumb, projects should currently:
<h2 id="faqs">FAQs<a class="headerlink" href="#faqs" title="Permanent link">&para;</a></h2>

- **How do I archive an old release?** `downloads.apache.org` is automatically archived every four hours. Therefore, a copy of every official release exists in the archives. Just delete the copy of the release that is in your project's dist directory. Remember to update any links from the download page related to that release.

**Note**: if your project is using the [Apache Trusted Releases](atr.html) (ATR) platform, there is no delay in archiving older releases.

@dave2wave dave2wave Aug 11, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PMC can configure the project so that archival of older releases is automated.