You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2026/09/15 21:05:05 UTC

(maven-site) 01/01: add ATR instructions in parallel to manual ones

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

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

commit 325082b052887c24cf4ea91d9eda9d31f430aa4a
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Tue Sep 15 23:04:53 2026 +0200

    add ATR instructions in parallel to manual ones
---
 .../developers/release/maven-project-release-procedure.md  | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/content/markdown/developers/release/maven-project-release-procedure.md b/content/markdown/developers/release/maven-project-release-procedure.md
index 617b6c95..b18fbc6e 100644
--- a/content/markdown/developers/release/maven-project-release-procedure.md
+++ b/content/markdown/developers/release/maven-project-release-procedure.md
@@ -81,13 +81,18 @@ mvn -Preporting site site:stage
 
 1. Follow the release preparation, **staging** and **closing** the repository steps outlined in [Publishing Maven Releases](https://infra.apache.org/publishing-maven-artifacts.html).
 
-   Staging repository **MUST** be closed with message like `VOTE Maven component name x.y.z`
+   Staging repository **MUST** be closed with message like `VOTE Maven component name x.y.z`.
+
+   If you want to automatically upload to [ATR](https://releases.apache.org/committees/maven),
+   use the [`push-to-atr` profile](/pom/asf/#the-push-to-atr-profile): `mvn release:perform -Ppush-to-atr`.
 
 2. Stage the latest documentation as explained in [deploying Maven components reference documentation](../website/deploy-component-reference-documentation.html).
 
 ## Call the vote
 
-Propose a vote on the dev list with the closed issues, the issues left, the staging repository and the staging site. For instance:
+Propose a vote on the dev list with the closed issues, the issues left, the staging repository and the staging site.
+
+This can be done either by hand or with ATR's help. For instance:
 
 ```
 To: "Maven Developers List" <de...@maven.apache.org>
@@ -119,11 +124,12 @@ Vote open for at least 72 hours.
 [ ] +1
 [ ] +0
 [ ] -1
-
 ```
 
 ## Check the vote results
 
+If using ATR, vote result can be automated. If still doing manual vote, you can follow classical manual instructions:
+
 The "vote is open for at least 72 hours" means that you need to wait _at least_ 72 hours before proceeding. This gives others time to test your staged release and check that everything is good, with the help of our [Guide to testing staged releases](/guides/development/guide-testing-releases.html).
 
 If after that period you have not received enough +1 votes to reach the quorum, this doesn't mean the vote failed: it just takes a bit longer.
@@ -192,6 +198,8 @@ Start the process for version `Y.Z+1` from the beginning.
 
 The official Apache release is the 'source-release' bundle distributed in `www.apache.org/dist`, as described in [Apache Release Distribution Policy](https://www.apache.org/dev/release-distribution). All releases for Maven must be copied to [the official Maven release area](https://www.apache.org/dist/maven/).
 
+This task can also be done by ATR, but following instructions remain here for manual process reference:
+
 The release area is maintained with svnpubsub. To deliver a release, you add it to [the subversion repository for the dist area](https://dist.apache.org/repos/dist/release/maven): add the release, its signature and sha512 checksum files, copying them from `target/checkout/target/` directory created during `mvn release:perform` step. Currently this requires to be in maven-pmc group (see [INFRA-5945](https://issues.apache.org/jira/browse/INFRA-5945)). If you are not a PMC member, drop a li [...]
 
 ```