...
Running mvn release:prepare will executes the following steps
- Check that there are no uncommitted changes in the sources
- Check that there are no SNAPSHOT dependencies
- Change the version in the poms from x-SNAPSHOT to a new version (you will be prompted for the versions to use)
- Transform the SCM information in the POM to include the final destination of the tag
- Run the project tests against the modified POMs to confirm everything is in working order
- Tag the code in the SCM with a version name (this will be prompted for)
- Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for)
- NOTE: since we're running the release from the branch, and you want this branch name to match up with the version in the pom.xml files within the branch, use the same name on this "development version" prompt that you used on the "release version" prompt. We'll update the pom.xml files in trunk by hand after a successful release vote.
- Commit the modified POMs
You'll have to build some modules by hand to prepare your local repository for the release:perform: (wiki note: why is this needed?)
...
Running mvn release:perform will executes the following steps
- Checkout from the tag
- Build the project and deploy all artifacts to Nexus temporary staging repository while gpg signing all artifacts.
3. Close the staging repository
...
If the vote is unsuccessful, the process will need to be restarted
- Rollback changes done to POMs
- delete tag from SCM manually
- Login to Nexus, and "Drop" the release from the staging repository
6. Successful wink-dev Voting, Call the general@incubator vote
...