How to create and announce a Camel release.
This release guide is based on the General guide for releasing Maven-based projects at Apache, so be sure to check it out before continuing and meet all prerequisites.
Note: Make sure that you are using JDK 6.
To prepare or perform a release you MUST BE at least an Apache Camel committer.
- The artifacts for each and every release must be SIGNED; your public key should be added to the KEYS file
- Your public key must also be cross-signed by other Apache committers (this can be done at key signing parties at ApacheCon for instance)
- Make sure you have the correct maven configuration in ~/.m2/settings.xml
- Use Maven 2.2.1+ (Maven 2.1.x is known to produce wrong gpg pom signatures - MGPG-14)
- From Camel 2.10 onwards we will require to use Maven 3.0.2+
- From Camel 2.11 onwards we will require to use Maven 3.0.4+
- You may want to get familiar with the release settings in the parent apache POM.
- Make sure you have installed Prince to be able to generate the Camel manual
- Add your Prince installation bin directory to your PATH variable:
Maven 2 Setup
Before you deploy anything to the maven repository using Maven 2, you should configure your ~/.m2/settings.xml file so that the file permissions of the deployed artifacts are group writable. If you do not do this, other developers will not able to overwrite your SNAPSHOT releases with newer versions. The settings follow the guidelines used by the Maven project. Please pay particular attention to the password encryption recommendations.
It is also essential that you configure your umask to 2 on people.apache.org for non-interactive login. You can do that by including the snipped below in your .profile.
Creating the Camel Release
The release plugin will prompt for a release version, tag and next release version. Use a three digit release version of the form: 2.x.x and for the tag use a string of the form: camel-2.x.x. The next version string should use the two digit from: 2.x-SNAPSHOT as this can be consistent for future SNAPSHOT releases.
- Grab the latest source from SVN
- Verify headers with rat
mvn -e org.apache.rat:apache-rat-plugin:check
grep -e ' !?????' target/rat.txt -- will show any files without licenses
- Do a release dry run to check for problems
mvn release:prepare -DdryRun=true
Check that you are happy with the results. The poms for the proposed tags will be in pom.xml.tag. Check also the generated signature files:
cmueller$ gpg camel-core/target/camel-core-2.7.5-SNAPSHOT.jar.asc
gpg: Signature made Tue Jan 10 20:50:27 2012 CET using RSA key ID 2A239C2C
gpg: Good signature from "Christian Mueller (CODE SIGNING KEY) <email@example.com>"
When you like the results, clean up:
- Prepare the release
This will create the tag in svn and leave various stuff around locally to direct the perform phase.
|Note: If you're located in Europe then release:prepare may fail with 'Unable to tag SCM' and 'svn: No such revision X'. Wait 10 seconds and run
- Perform the release to the staging repo
- Close the staging repository
Quote from the Maven release guide for Apache projects
Login to https://repository.apache.org using your Apache LDAP credentials. Click on "Staging Repositories". Then select "org.apache.camel-xxx" in the list of repositories, where xxx represents your username and ip. Click "Close" on the tool bar above. 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.
See the image in the original guide for more info.
- Verify staged artifacts
Quote from the original guide
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.
Testing the Camel Release Candidate
When folks need to test out a release candidate, the jars will not have been uploaded to the central Maven repo. This means that the example programs which use Maven will not automatically work and you need to follow the Testing a release candidate guidelines.
Afterwards send out the VOTE for this release candidate to the dev@ mailing list.
Manually updating files
The pom.xml files in etc, tests/camel-itest-karaf, tests/camel-itest-osgi, tests/camel-itest-performance and tests/camel-performance need to be manually updated with the Camel version number in the <parent> tag.
Announcing the Camel Release
If the VOTE pass,
- Close it by sending the RESULT to the mailing list.
- Promote the artifacts to the central repo. For this login to https://repository.apache.org using your Apache LDAP credentials. Click on "Staging Repositories". Select "org.apache.camel-xxx" in the list of repositories, where xxx represents your username and ip. Click "Release" on the tool bar above. This will promote all artifacts to the central maven repo. Enter the name and version of the artifact being released in the "Description" field and then click "Release". This will make it easier to identify it later.
- Perform a release in JIRA and create a new release version in JIRA
- There should be already a release notes page in the In Progress folder (if not create one based on the Camel x.y.z Release (template)). Edit it and change the number of fixed issues and update its parent to be the Download page. Now would be a good time to create a new release notes page for the next release based on the template mentioned before. It is useful and simpler to keep it up to date during the development cycle.
- Copy the newly deployed distribution to Apache website:
release-distro.sh <Camel version>
Check the console output and finish this step manually after checking the artifacts.
- Copy the KEYS file by ssh into /www/www.apache.org/dist/camel/apache-camel/ on people.apache.org if you changed it
- Update the Download page to refer to the latest release distributions (search & replace the version numbers mostly)
- Upload the newly deployed schema and the manual to Apache:
release-website.sh <Camel version>
Check the console output and finish this step manually after checking the artifacts.
- Upload the javadocs to Apache, you need to checkout the files from "https://svn.apache.org/repos/infra/websites/production/camel/content/maven/"
|Using SVN the first time on people.apache.org|
To be able to perform a checkout on people.apache.org from svn.apache.org, you have to trust the server certificate:
svn list "https://svn.apache.org/repos/infra/websites/production/camel/content"
Error validating server certificate for 'https://svn.apache.org:443':
The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually!
Valid: from Tue, 20 Dec 2011 00:00:00 GMT until Mon, 17 Feb 2014 23:59:59 GMT
Issuer: Thawte, Inc., US
(R)eject, accept (t)emporarily or accept (p)ermanently?
- Copy $CAMEL_ROOT/trunk/etc/scripts/release-website.sh to your home directory on people.apache.org
- Execute this script, e.g: ./release-website.sh 2.10.0
- It will download the XML Schema files and the Camel manual for the given release version
- At the end you have to commit these changes manually to SVN (simply follow the instructions)
- Update the Xml Reference page with a link to the XSD's
- Update the Manual page with a link to the PDF/HTML if it's a new major/minor version
- Mail the dev, user & announce lists
- Post a news entry in the wiki which links to the release page so folks can download it!
- perform a full export of the Camel WIKI sites to see your blog on the Camel index site. To do this, you have to remove the main.pageCache file in the content/cache sub directory:
- execute: svn rm https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache
- Add the release version number to the following spring.schemas file located in src/main/resources/META-INF directory of the following components:
- Have a beer!
Create a new maintenance branch
When we finish the major version release, we need to create a maintenance branch to holds the bug fixes. Here are the steps for it.
- Create a branch from trunk remotely
svn copy -m "create camel 2.10.x fix branch" https:
- Check out the remote branch in a new directory
- Initialize merge tracking for the new branch
svnmerge.py init -f commit.txt https:svn ci -F commit.txt
- Update the version number for the next patch release
find ./ -name pom.xml |xargs perl -pi -e 's/2.11-SNAPSHOT/2.10.x-SNAPSHOT/g'
svn ci -m "Update the pom version for next patch release"
- Set up a new continuous integration build, if we release a new major/minor version: https://builds.apache.org/view/A-D/view/Camel/