THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Archiva Release Process
- If there are changes in the parent pom, release parent pom – https://svn.apache.org/repos/asf/maven/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/maven/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
- 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'
- 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.
- ssh to people@apache.org and copy the binaries, sources, checksums, wars and docs from the staging repository to www/people.apache.org/builds/maven/archiva/
- Download the uploaded files via wget:
ex. wget http://people.apache.org/builds/maven/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 site (mvn site:stage-deploy -DstagingSiteURL=scp://people.apache.org/home/brett/staging-sites/archiva/1.0.1) from the archiva-1.0.x tag
- 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.
- After the vote has passed, copy the sources and binaries from people.apache.org to www.apache.org/dist/maven.
- 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
- Publish the docs (mvn site-deploy) from the archiva-1.0.x tag
- Update the archiva site (https://svn.apache.org/repos/asf/maven/archiva/site/) for the versions and release notes URL and run 'mvn site-deploy'
- Publish the reference docs (mvn site-deploy) from the archiva-1.0.x tag. (You may have to exclude the archiva-webapp module to do this)