Skip to content

Cottage14 patch atr pages related to ATR - #302

Open
cottage14 wants to merge 5 commits into
masterfrom
cottage14-patch-atr
Open

Cottage14 patch atr pages related to ATR#302
cottage14 wants to merge 5 commits into
masterfrom
cottage14-patch-atr

Conversation

@cottage14

Copy link
Copy Markdown
Contributor

No description provided.

@cottage14
cottage14 requested a review from dave2wave August 11, 2026 17:17
Comment thread content/pages/atr.md

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>.

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 ...


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.

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.

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.

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.


- **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.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants