This is an automated email from the ASF dual-hosted git repository.

slawekjaranowski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new c8c93612 Describe ATR usage in Maven core release procedure
c8c93612 is described below

commit c8c936129c49740d9ae2355bf7ddc2a0f5e40716
Author: Slawomir Jaranowski <[email protected]>
AuthorDate: Thu Nov 5 19:35:52 2026 +0100

    Describe ATR usage in Maven core release procedure
    
    Mark the steps in the Maven core release procedure which are not needed
    or done by ATR, and link the dedicated Maven core vote template.
    
    Also update ATR notes in the common release procedure:
    ATR copies the source release to the distribution area
    and removes superseded releases.
    
    Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
 .../markdown/developers/release/maven-core-release.md  | 18 +++++++++++++++++-
 .../release/maven-project-release-procedure.md         |  5 +++--
 2 files changed, 20 insertions(+), 3 deletions(-)

diff --git a/content/markdown/developers/release/maven-core-release.md 
b/content/markdown/developers/release/maven-core-release.md
index df46dd90..40c5ab4f 100644
--- a/content/markdown/developers/release/maven-core-release.md
+++ b/content/markdown/developers/release/maven-core-release.md
@@ -44,6 +44,10 @@ https://dist.apache.org/repos/dist/dev/maven/maven-3/
           `-- apache-maven-$VERSION-src.zip.sha512
 ```
 
+**NOTE** When releasing with the [Apache Trusted Releases 
(ATR)](./maven-project-release-procedure.html#release-with-the-apache-trusted-releases-atr),
+the release candidate is uploaded to `ATR` instead of the svn `dev` tree,
+and `ATR` promotes it to the `release` tree after a successful vote.
+
 Note that the policy for failed releases is to move forward with a new
 version. The tag that produced the failed released is left in place for
 posterity. So if the release of, say, 3.2.4 fails then we move forward
@@ -57,6 +61,8 @@ Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 
then create the ne
 
 Copy the binaries and src-tar.gz with their sha512/asc to the created 
directories.
 
+With `ATR`, the two steps above are not needed, the distribution archives are 
uploaded to `ATR` by `mvn release:perform -Ppush-to-atr`.
+
 To produce a release candidate, follow the first seven steps only from the 
following procedure:
 
 - [Maven Project Common Release 
Procedure](./maven-project-release-procedure.html)
@@ -99,6 +105,10 @@ mvn scm-publish:publish-scm
 
 This will publish the Maven core site in [/ref/3-LATEST](/ref/3-LATEST).
 
+This step is still required with `ATR`. The Maven core vote template
+[start_vote_template_maven.txt](/atr/templates/start_vote_template_maven.txt) 
links to this staged site
+as `https://maven.apache.org/ref/{{MAJOR_VERSION}}-LATEST`.
+
 ## Complete the release
 
 After a successful vote you should do the following steps to finish the 
release.
@@ -106,7 +116,9 @@ After a successful vote you should do the following steps 
to finish the release.
 ### Add New Version to ASF Distribution Directory
 
 In addition to promoting the repository, the release archives should be
-moved to the release svnpubsub tree:
+moved to the release svnpubsub tree.
+
+This task is done by `ATR` after a successful vote, but following instructions 
remain here for manual process reference:
 
 ```
 svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/$VERSION 
https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Publish Maven 
$VERSION Distribution Archives"
@@ -150,7 +162,11 @@ Commit your changes and then [deploy the main Maven 
site](../website/deploy-mave
 
 Next, any superseded releases should be removed from the above locations 
(after confirming that they exist in /www/archive.apache.org/dist/maven).
 
+With `ATR`, this step is not needed, superseded releases are removed by `ATR`.
+
 ### Proceed with Announcement
 
 You can now proceed with the steps outlined after deploying the website on 
[Maven Project Common Release Procedure](./maven-project-release-procedure.html)
 
+With `ATR`, the announcement is sent from `ATR`.
+
diff --git 
a/content/markdown/developers/release/maven-project-release-procedure.md 
b/content/markdown/developers/release/maven-project-release-procedure.md
index c23bc67e..756c7165 100644
--- a/content/markdown/developers/release/maven-project-release-procedure.md
+++ b/content/markdown/developers/release/maven-project-release-procedure.md
@@ -96,10 +96,10 @@ Prepare local environment for `ATR Maven Plugin` usage, see 
[ATR Maven Plugin](h
 2. Start a new release by providing the version
 3. Upload the 'source-release' with `mvn release:perform -Ppush-to-atr` 
([`push-to-atr` profile](/pom/asf/#the-push-to-atr-profile))
 4. Start the vote and wait for the result
-5. After the vote is successful, `ATR` will promote the 'source-release' to 
the Apache distribution area, **NOTE** old releases are not removed yet
+5. After the vote is successful, `ATR` will promote the 'source-release' to 
the Apache distribution area and remove superseded releases
 6. Finish the release by sending the announcement in `ATR`
 
-With `ATR`, you can skip only `Vote` and `Announce` steps, as `ATR` will take 
care of them, 
+With `ATR`, you can skip only `Vote`, `Copy the source release to the Apache 
Distribution Area` and `Announce` steps, as `ATR` will take care of them, 
 rest of the steps are still required to be done by the release manager.
 
 ## Call the vote
@@ -229,6 +229,7 @@ wagon/wagon-2.2-source-release.zip.sha512
 ```
 
 You should also run 'svn rm' as needed to clear out older releases. As per 
[Apache Release 
Policy](https://www.apache.org/legal/release-policy.html#where-do-releases-go), 
only the latest release on a branch should stay in the main dist areas. So long 
as the previous release is at least a day old, the automatic archiver will have 
copied it to the archive.
+With `ATR`, superseded releases are removed by `ATR`.
 
 To check that everything is ok in the dist area, dist-tool-plugin has been 
written and run once a day to produce ["Check Source Release" and "Check 
Errors" 
reports](https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/).
 

Reply via email to