[CONF] Apache Camel > Release Guide

[willem jiang (Confluence)]

willem jiang edited the page: Release Guide ... 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: Code Block language text cd ${CAMEL_ROOT_DIR}/etc/scripts release-distro.sh <Camel version> Check the console output and finish this step 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" 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> 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/" 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? 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: camel-cxf camel-spring camel-spring-integration camel-spring-security Have a beer! ... View Online · Like · View Changes Stop watching space · Manage Notifications This message was sent by Atlassian Confluence 5.0.3, Team Collaboration Software