THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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 - 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.Code Block xml xml <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
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
'
- Make sure that you have the "release" profile set in your
- 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:
No Format ex. wget http://people.apache.org/builds/archiva/1.0.1/apache-archiva-1.0.1-bin.tar.gz
- Verify the signatures:
No Format ex. gpg -v apache-archiva-1.0.1-bin.zip.asc
- Verify the checksums:
No Format 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/public_html/staging-sites/archiva/1.0.1)
from the archiva-1.0.x release 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. example
- 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:
No Format 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
in thearchiva-docs
directory) from the archiva-1.0.x release tag - 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 thearchiva-modules
directory) from the archiva-1.0.x release tag. (You may have to exclude thearchiva-webapp
module to do this) - Send out an announcement of the release