This is an automated email from the ASF dual-hosted git repository. wave pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tooling-docs.git
The following commit(s) were added to refs/heads/main by this push: new d68be89 Update infrastructure requirements d68be89 is described below commit d68be89866e29d265113fb9b9b19fa2d785c299c Author: Dave Fisher <dave2w...@comcast.net> AuthorDate: Thu Feb 6 13:04:11 2025 -0800 Update infrastructure requirements --- apache-trusted-release/requirements.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/apache-trusted-release/requirements.md b/apache-trusted-release/requirements.md index 6efe612..495e6e6 100644 --- a/apache-trusted-release/requirements.md +++ b/apache-trusted-release/requirements.md @@ -63,16 +63,18 @@ While reading consider these Notes: Here is a flow chart showing the [Release Lifecycle Phases](lifecycle.md). -## 6. Additional Requirements +## 6. Infrastructure Requirements - - Retire dist.apache.org svn repository once all 200+ PMCs have fully switched over to directly using the **ATR**. - - Continue to support legacy urls for dist.apache.org, downloads.apache.org, dlcdn.apache.org, and archive.apache.org + - Run book for releases.apache.org + - Progress on the retirement path for `svn:dist`. See [Legacy Releases from SVN Dist](svn-dist.md) + for possible transitional states. For this first iteration _transition 2_ is preferred. + - Assure support legacy urls for dist.apache.org, downloads.apache.org, dlcdn.apache.org, and archive.apache.org ## 7. Future Requirements - Integrate with the [Security Advisory Process](advisory-process.md) to make it easy to track applicable advisories on download pages. - Expand support for [Evaluating Build Claims](evaluate.md) to additional build tools. - Expand automated support for additional [Distribution Channels](distributions.md). - - [Signing Candidates](./digital-signatures.md) during ATR processing is deferred. For now, creating digital signatures on certain artifact types - must be done prior to GPG signing and prior to submission of the release candidate. + - [Signing Candidates](./digital-signatures.md) during ATR processing is deferred. For now, creating digital signatures on + certain artifact types must be done prior to GPG signing and prior to submission of the release candidate. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org For additional commands, e-mail: dev-h...@tooling.apache.org