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
2. Deploy a Snapshot
This is useful to verify your settings in ~/.m2/settings.xml (Nexus password and GPG key)
3. Prepare the Release
|When asked for the SCM release tag please remove the studio-plugin prefix, the version number is enough.|
This creates a tag here: http://svn.apache.org/viewvc/directory/studio-plugin/tags/
4. Stage the Release
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
This creates and deploys the site via ssh to people.apache.org/www/directory.apache.org/studio-plugin/gen-docs.
5. Inform dev list
For internal projects we use a simplified release process http://email@example.com/msg29764.html. Inform the dev list to publish (release) the Studio Maven Plugin project. After a 4 hr grace period the Studio Maven Plugin project can be released, therefor go to https://repository.apache.org/index.html#stagingRepositories and release the staging repository.