THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
When the build is done staging, you need to login to the Nexus repository and "close" the staging area. See the Maven page for instructions. This is very important. After the staging area is closed, note the URL for the staging area as you will need it for the vote.
...
4. Call the wink-dev vote
...
Propose a vote on the dev list. Be sure to provide the staging repository, the staging site, release SCM tag and revision number. For instance:
...
- 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
...
7. Successful general@incubator vote
...
If the vote passes, you'll need to promote that staging repository to the main location. Login to Nexus to do that as well. See Maven team release page for more details.
...
...
8. Copying distributions to Apache
...
Copy the actual distributions (all artifacts located under apache-wink in Nexus repo) to people.apache.org:/www/www.apache.org/dist/incubator/wink.
...
...
9. Update Wink site
...
- Check out Wink site from https://svn.apache.org/repos/asf/incubator/wink/site
- Update Wink Java-Docs by:
- Download & extract Java-Docs from distribution source archive
- Create new directory under /wink/site/trunk/site/src/site/resources/VERSION and copy extracted Java-Docs
- Update Wink site Download page with new Wink release artifacts
- Follow instructions located under /wink/site/trunk/site/how-to.txt to rebuild the site
...
...
10. Update pom.xml files in trunk
...
Once the release is successful, and since we ran the release from a branch, the pom.xml files in trunk still have the old version number. You will want to update the version in all of the pom.xml files throughout the project; for example, from 1.1-incubating-SNAPSHOT to 1.2-incubating-SNAPSHOT.
...