Maven differs slightly in its release process due to several extra steps and this need to be publish via Apache svnpubsub.
The goal is to commit candidate release to svn tree https://dist.apache.org/repos/dist/dev/maven/maven-3/$VERSION. Then once the vote passed svn move to https://dist.apache.org/repos/dist/release/maven/maven-3/$VERSION.
The tree directory is:
For non-alpha/beta releases, release candidates are produced before the actual release.
Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then create the necessary directory tree.
Copy the binaries and src-tar.gz with their md5/asc to the created directories.
To produce a release candidate, follow the first seven steps only from the following procedure:
The version used should be the eventual version with -RC1, -RC2, etc. appended.
After producing the RC, request that the developers test the release on the list. If a regression is found, a new release candidate is rolled.
After a reasonable time without regressions found, a wider audience may be polled if the release manager desires (for example, users@).
Once happy with a release candidate, the full release is performed, with the final version in place.
To produce a final release, the same process as for standard projects is followed:
Below describes the additional steps that need to be taken at the points where the website are updated in those instructions.
Edit https://svn.apache.org/repos/asf/maven/maven-3/trunk/doap_Maven.rdf to list the new release.
Note that release notes can be created and checked in, but other changes should not be checked in as it can be deployed 'live' at any time.
Next, create the release notes:
Only deploy the site once the release is present on the mirrors, and the reference documentation has been deployed to /ref/.
Once the release is prepared, but before the release vote, the site needs to be staged.
mvn -Preporting site site:stage-deploy -DstagingSiteURL=scp://people.apache.org/home/$USER/public_html/staged-sites/maven-$VERSION
Note: It requires Maven 2.1.0 or higher to successfully deploy to people.apache.org via SSH. Older Maven versions will fail due to com.jcraft.jsch.JSchException: Algorithm negotiation fail.
Some developers have reported problems with the site:stage-deploy goal. In that case, you can stage the site locally and upload it manually:
mvn -Preporting site site:stage scp -r target/staging/people.apache.org/home/$USER/public_html/staged-sites/maven-$VERSION USER@people.apache.org:/home/$USER/public_html/staged-sites/maven-$VERSION
In addition to promoting the repository, the release archives should be moved to the release svnpubsub tree :
The source code references and API docs need to be deployed before deploying the web site with the new version.
This is described in Deploying the Current References.
Once both of the above have synced to the main site and a suitable number of mirrors, proceed to update the web site and produce the announcement.
Commit your changes and then deploy the main Maven site checked out earlier.
mvn -Preporting clean site-deploy
Next, any superceded releases should be removed from the above locations (after confirming that they exist in /www/archive.apache.org/dist/maven).
You can now proceed with the steps outlined after deploying the website on Maven Project Common Release Procedure
Note: For Maven core releases, the announcement is additionally sent to firstname.lastname@example.org. This is best done as a separate message to avoid cross-posting replies.