[CONF] Apache Camel > Release Guide

[willem jiang (Confluence)]

willem jiang edited the page: Release Guide ... 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 From Camel 2.10 onwards we will require to use Maven [3.0.2,3.1.0) From Camel 2.11 onwards we will require to use Maven [3.0.4,3.1.0] 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: Code Block language text PATH=$PATH:/usr/local/bin/prince 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. ... Create a new maintenance branch Info title This section is out of date. This section just for creating a maintenance branch in camel svn repo, it is much easy to create a new branch after camel repo is switched to Git.   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. ... View Online · Like · View Changes Stop watching space · Manage Notifications This message was sent by Atlassian Confluence 5.0.3, Team Collaboration Software