Here you will find the steps to create releases for Tiles.
Apache's existing documentation should be read
To create a release you have to install:
These operations need to be performed only one time.
To create a GPG key, follow the guidelines. Include it in:
https://svn.apache.org/repos/asf/tiles/site/KEYS
Publish your GPG key in a PGP key server, such as MIT Keyserver.
Your settings.xml must be modified to allow deployment.
See Publishing Maven Artifacts – Setup your development environment
These steps must be performed for each release.
To prepare the release Subversion tag, check out the branch/trunk from where you are preparing the release and type:
mvn clean mvn release:prepare -Dusername=YOUR_SVN_USER -Dpassword=YOUR_SVN_PASSWORD
The plugin interactively will ask you the version to release, the Subversion tag to use and the next snapshot version. It is recommended to use the tag: tiles-request-X.X.X.
See also the recommendations of the ASF.
To perform the release, i.e. creating and deploying Maven artifacts, use:
mvn release:perform
It should compile and test everything, build and upload the artifacts and the website for the project.
Upload the assemblies manually with
cd target/
svn co https://dist.apache.org/repos/dist/dev/tiles tiles-dist-dev
mkdir tiles-dist-dev/request/${version}
cp checkout/assembly/target/assemblies/* tiles-dist-dev/request/${version}/
svn add tiles-dist-dev/request/${version}
svn ci tiles-dist-dev/request/${version}Login to Nexus repository using your Apache LDAP credentials. Click on "Staging". Then click on "tiles" in the list of repositories.
In the panel below you should see an open repository that is linked to your username and ip. Right click on this repository and select "Close". This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything.
Enter the name and version of the artifact being released in the "Description" field and then click "Close". This will make it easier to identify it later.
If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of *.asc (signature) files. If the you don't like the content of the repository, right click your repository and choose "Drop". You can then rollback your release and repeat the process.
Note the repository URL, you will need this in your vote email.
In developers mailing list send an announcement for the test build:
Subject: [ANNOUNCE] Tiles Request ${version} test build available
The test build of Tiles Request ${version} is available.
No determination as to the quality ('alpha,' 'beta,' or 'GA') of Tiles Request
${version} has been made, and at this time it is simply a "test build". We
welcome any comments you may have, and will take all feedback into
account if a quality vote is called for this build.
Release notes:
* ${jira.release.notes}
Distribution:
* https://dist.apache.org/repos/dist/dev/tiles/request/${version}/
Maven 2 staging repository:
* https://repository.apache.org/content/repositories/tiles-[YOUR REPOSITORY ID]/
A vote regarding the quality of this test build will be initiated
within the next couple of days.A few days after the test build announcement, call for a vote in developers mailing list.
Subject: [VOTE] Tiles Request ${version} Release Quality
The Tiles Request ${version} test build has been available since ${testBuildDate}.
Release notes:
* ${jira.release.notes}
Distribution:
* https://dist.apache.org/repos/dist/dev/tiles/request/${version}/
Maven 2 staging repository:
* https://repository.apache.org/content/repositories/tiles-[YOUR REPOSITORY ID]/
If you have had a chance to review the test build, please respond with
a vote on its quality:
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[ ] General Availability (GA)
Everyone who has tested the build is invited to vote. Votes by PMC
members are considered binding. A vote passes if there are at least
three binding +1s and more +1s than -1s.After a vote is finished, and it has been decided that is at least of alpha quality, there is the need of a post-vote process.
Once the release is deemed fit for public consumption it can be transfered to a production repository where it will be available to all users.
Login to Nexus repository again. Click on "Staging" and then on the repository with id "tiles-staging". Find your closed staging repository, right click on it and choose "Release".
Next click on "Repositories", select the "Releases" repository and validate that your artifacts exist as you expect them.
Move assemblies into the Apache dist repository:
svn mv https://dist.apache.org/repos/dist/dev/tiles/request/${version} https://dist.apache.org/repos/dist/release/tiles/request/Wait 24 hours to let the mirror sync to the release and then update the site. In particular you have to update the index and the download pages:
https://svn.apache.org/repos/asf/tiles/site/src/site/xdoc/index.xml https://svn.apache.org/repos/asf/tiles/site/src/site/apt/download.apt
Build and publish the site:
mvn clean site site:stage mvn scm-publish:publish-scm # check staging website at target/scmpublish-checkout/index.html cd <tiles-site-checkout>/publish/tiles-request/ svn merge ^/tiles/site/staging/tiles-request . svn ci
Finally, send an an announcement to the users and developers mailing list:
Subject: [ANNOUNCE] Tiles Request ${version} ${quality} released
The Apache Tiles team is pleased to announce the release of Tiles Request ${version}
${quality}.
Available in binary and source distribution.
http://tiles.apache.org/download.html
It is also available in the central Maven repository under Group ID
"org.apache.tiles".
The 1.0.x series of the Apache Tiles Request framework has a minimum
requirement of the following specification versions:
* Java Servlet 2.5 and JavaServer Pages (JSP) 2.1
* Java Standard Edition (Java SE) 1.7
The release notes are available online at:
* ${jira.release.notes}
Please feel free to test the distribution and post your comments to
the user list, or, if appropriate, file a ticket with JIRA.