Page History

...

1. Post to the dev list a few days before you plan to do an Archiva release
2. Recreate the staging repository on VMBuild
3. 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)
4. 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
5. Update the release notes and the site.xml for version changes in archiva-docs
6. 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.
7. Release archiva
   • Make sure that you have the "apache-release" profile set in your settings.xml as shown below.

     Code Block
     xml xml
     <profile> <id>apache-release</id> <properties> <gpg.passphrase>[GPG_PASSWORD]</gpg.passphrase> </properties> </profile>

   • Set your user credentials for the stage repo in the <servers> section of your settings.xml for vmbuild.staging

   • Wiki Markup
     Execute {{mvn release:prepare}} (check that it has been properly tagged. the tag name must be.. {{archiva-\[VERSION\]}})

   • Then execute mvn release:perform
8. Download the uploaded files via wget:

   No Format
   ex. wget http://vmbuild.apache.org/archiva/repository/staged-releases/org/apache/archiva/archiva-jetty/1.3/archiva-jetty-1.3-bin.tar.gz

9. Verify the signatures:

   No Format
   ex. gpg -v archiva-jetty-1.3-bin.zip.asc

10. Stage the documentation to the staging repository, by executing the following command in the archiva-docs module of the tagged version:

    No Format
    mvn site:stage-deploy -DstagingSiteURL=scp://[USERNAME]@people.apache.org/PATH/TO/STAGE/DIR

11. 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
12. 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.
13. After the vote has passed, copy the sources and binaries from people.apache.org org/apache/archiva/archiva-jetty and org/apache/archiva/archiva to /www/www.apache.org/dist/archiva. They will need to be renamed to match conventions of previous releases.
14. To sync the jars to ibiblio, execute:

    No Format
    mvn stage:copy -Dsource="[STAGE_REPO_URL]http://vmbuild.apache.org/archiva/repository/staged-archiva" -Dtarget="scp://[APACHE_USERNAME]@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" -Dversion=21.3 -DrepositoryId=apache.releases

15. 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
16. Remove old versions from /www/www.apache.org/dist/archiva
17. 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
18. Send out an announcement of the release