...
- 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, and make sure to remove the (release in progress) in the title. 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:
Code Block language text cd ${CAMEL_ROOT_DIR}/etc/scripts release-distro.sh <Camel version>
Check the console output and finish this step (run svn ci) manually after checking the artifacts.
- Remove the old release by using svn rm https://dist.apache.org/repos/dist/release/camel/apache-camel/OLD_CAMEL_VERSION -m "Removed the old release"
- Update the download link of the Camel x.y.z Release to with http://archive.apache.org/dist/
- 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:
Code Block language text cd ${CAMEL_ROOT_DIR}/etc/scripts ./release-website.sh <Camel version>
The script will download the website release artifacts using wget. Once all artifacts are downloaded, the following message is displayed:
Code Block NOTE: Manual steps required! Check the schemas and manual files for new artifacts, add them to the repository as required and commit your changes. This step is intentionally not automated at this point to avoid errors. cd /tmp/camel-release/websites/production/camel/x.y.z/schema/ svn status svn add <schema-x.y.z-qualifier>.xsd svn ci -m "Uploading released schemas for camel-x.y.z" cd /tmp/camel-release/websites/production/camel/x.y.z/manual/ svn status svn add camel-manual-x.y.z.html svn ci -m "Uploading released manuals for camel-x.y.z"
Finish this step by following the provided command sequence unsing svn 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/"
Info title 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:
No Format 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! Certificate information: Hostname: *.apache.org Valid: from Tue, 20 Dec 2011 00:00:00 GMT until Mon, 17 Feb 2014 23:59:59 GMT Issuer: Thawte, Inc., US Fingerprint: bc:5f:40:92:fd:6a:49:aa:f8:b8:35:0d:ed:27:5e:a6:64:c1:7a:1b (R)eject, accept (t)emporarily or accept (p)ermanently?
- 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@camel.apache.org, users@camel.apache.org & announce@apache.org 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:
- Add the release version number to the following
spring.schemas
file located insrc/main/resources/META-INF
directory of the following components:- camel-cxf (/camel/components/camel-cxf/src/main/resources/META-INF/spring.schemas)
- camel-spring (/camel/components/camel-spring/src/main/resources/META-INF/spring.schemas)
- camel-spring-integration (/camel/components/camel-spring-integration/src/main/resources/META-INF/spring.schemas)
- camel-spring-security (/camel/components/camel-spring-security/src/main/resources/META-INF/spring.handlers)
- Have a beer!
Create a new maintenance branch
Info | ||
---|---|---|
| ||
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.
Create a branch from trunk remotely
Code Block language text svn copy -m "create camel 2.10.x fix branch" https://svn.apache.org/repos/asf/camel/trunk/ https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x
Check out the remote branch in a new directory
Code Block language text svn checkout https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x
Initialize merge tracking for the new branch
Code Block language text cd camel-2.10.x svnmerge.py init -f commit.txt https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x svn ci -F commit.txt
Update the version number for the next patch release
Code Block language text 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/
Code Block | ||
---|---|---|
| ||
mvn release:clean -Prelease |