Since we are using Nexus for releases the release process is as follows (see also http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven).
1. Prepare the Project
| No Format |
|---|
$ mvn release:prepare -DdryRun=true |
2. Deploy a Snapshot
| No Format |
|---|
$ mvn deploy |
This is useful to verify your settings in ~/.m2/settings.xml (Nexus password and GPG key)
3. Prepare the Release
| No Format |
|---|
$ mvn release:clean $ mvn release:prepare |
This creates a tag here: http://svn.apache.org/viewvc/directory/buildtools/skins/tags/
4. Stage the Release
| No Format |
|---|
$ mvn release:perform |
This deploys the release to a staging repository. Go to https://repository.apache.org/index.html#stagingRepositories and close the staging repository.
6. Deploy the Site
| No Format |
|---|
$ cd target/checkout $ mvn site-deploy |
This creates and deploys the site via ssh to people.apache.org/www/directory.apache.org/skins/gen-docs.
5. Inform dev list
For internal projects we use a simplified release process http://www.mail-archive.com/dev@directory.apache.org/msg29764.html. Inform the dev list to publish (release) the Skins project. After a 4 hr grace period the Skins project can be released, therefor go to https://repository.apache.org/index.html#stagingRepositories and release the staging repository.