Archiva Release Process

Post to the dev list a few days before you plan to do an Archiva release
If there are changes in the parent pom, release parent pom – https://svn.apache.org/repos/asf/archiva/parent
- mvn release:prepare (verify that it has been properly tagged)
- mvn release:perform (verify that it has been deployed correctly in the staging repo)
Update the parent pom version of archiva – https://svn.apache.org/repos/asf/archiva/trunk
- change the parent pom version to the archiva-parent version that has just been released
- commit the changes made
Update the release notes and the site.xml for version changes
Verify that the webapp-tests are building successfully. Since it is in a separate profile but inside the Archiva source tree, it will not be released but will still be included in the release tag. If some tests are failing, comment it out first so that only the passing tests are executed when the webapp-tests module are built from the tag.

Release archiva

Make sure that you have the "release" profile set in your settings.xml as shown below. The <deploy.altRepository> should hold the value of the stage repository where the release will be staged.

<profile>
  <id>release</id>
  <properties>
    <gpg.passphrase>[GPG_PASSWORD]</gpg.passphrase>
    <deploy.altRepository>apache.releases::default::scp://[HOSTNAME/PATH/TO/DIRECTORY/STAGE/REPO]</deploy.altRepository>
  </properties>
  <repositories>
    <repository>
      <id>apache.releases</id>
      <name>Apache Stage Repo</name>
      <url>[STAGE_REPO_URL]</url>     
    </repository>
  </repositories>
</profile>

Set your user credentials for the stage repo in the <servers> section of your settings.xml
Execute mvn release:prepare (check that it has been properly tagged. the tag name must be.. archiva-[VERSION])
Then execute mvn release:perform

ssh to people@apache.org and copy the binaries, sources, checksums, wars and docs from the staging repository to www/people.apache.org/builds/archiva/

Download the uploaded files via wget:

ex.
wget http://people.apache.org/builds/archiva/1.0.1/apache-archiva-1.0.1-bin.tar.gz

Verify the signatures:

ex.
gpg -v apache-archiva-1.0.1-bin.zip.asc

Verify the checksums:

ex.
md5sum apache-archiva-1.0.1-src.zip
cat apache-archiva-1.0.1-src.zip.md5

sha1sum apache-archiva-1.0.1-src.zip  
cat apache-archiva-1.0.1-src.zip.sha1

Stage the documentation to the staging repository, by executing the following command in the archiva-docs module of the tagged version:
```
mvn site:stage-deploy -DstagingSiteURL=scp://[USERNAME]@people.apache.org/PATH/TO/STAGE/DIR
```
Call for a vote in the dev list and wait for 72 hrs. for the vote results. 3 binding votes is necessary for the release to be finalized. example
If the vote fails or needs to be canceled, the version number should not be re-used if the version was made available for public download.
After the vote has passed, copy the sources and binaries from people.apache.org to /www/www.apache.org/dist/archiva.

To sync the jars to ibiblio, execute:

mvn stage:copy -Dsource="[STAGE_REPO_URL]"
     -Dtarget="scp://[APACHE_USERNAME]@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" 
     -Dversion=2.3 -DrepositoryId=apache.releases

Update the archiva site (https://svn.apache.org/repos/asf/archiva/site/) for the versions and release notes URL and run mvn site-deploy. Below are the list of pages that you need to update:
- src/site/xdoc/index.xml
- src/site/apt/known-issues.apt
- src/site/apt/versions.apt
- src/site/apt/download.apt
- src/site/resources/.htaccess - update Redirect Permanent /reports http://archiva.apache.org/ref/1.0.1 and Redirect Permanent /docs/current http://archiva.apache.org/docs/1.0.1/ to the latest released version
Remove old versions from /www/www.apache.org/dist/archiva
Publish the reference docs (mvn site-deploy in the archiva-modules directory) from the release tag. You may have to exclude the archiva-webapp module to do this, and will require MAVEN_OPTS=-Xmx256m
Send out an announcement of the release