You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2016/09/25 08:26:25 UTC
svn commit: r998190 [11/13] - in /websites/production/camel/content: ./
2007/08/17/ 2007/08/20/ 2007/10/01/ 2007/10/28/ 2008/04/08/ 2008/04/22/
2008/04/28/ 2008/07/22/ 2008/10/31/ 2009/01/19/ 2009/02/03/ 2009/02/17/
2009/03/17/ 2009/05/19/ 2009/06/15/ ...
Modified: websites/production/camel/content/release-guide.html
==============================================================================
--- websites/production/camel/content/release-guide.html (original)
+++ websites/production/camel/content/release-guide.html Sun Sep 25 08:26:21 2016
@@ -39,6 +39,7 @@
<link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css' rel='stylesheet' type='text/css' />
<link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css' rel='stylesheet' type='text/css' />
<script src='//camel.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
<script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
<script src='//camel.apache.org/styles/highlighter/scripts/shBrushPlain.js' type='text/javascript'></script>
@@ -168,15 +169,38 @@ gpg: Good signature from "Christian
</div></div><p>again.</p></div></div></li><li><p>Perform the release to the staging repo</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn release:perform -Prelease,apache-release
]]></script>
-</div></div></li><li>Close the staging repository<br clear="none"> Quote from the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">Maven release guide for Apache projects</a><blockquote><p>Login to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a> 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.</p></blockquote>See the screenshot below that shows the state of the
staging repository at this stage.<br clear="none"><br clear="none"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" height="250" src="release-guide.data/apache-nexus-close-repo.png" data-image-src="/confluence/download/attachments/68287/apache-nexus-close-repo.png?version=1&modificationDate=1448317837000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="61330078" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="apache-nexus-close-repo.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="68287" data-linked-resource-container-version="111"></span><br clear="none"><br clear="none"></li><li>Verify staged artifacts<br clear="none"> Quote from the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">o
riginal guide</a><blockquote><p>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.<br clear="none"> Note the repository URL, you will need this in your vote email.</p></blockquote></li></ol><h2 id="ReleaseGuide-TestingtheCamelReleaseCandidate">Testing the Camel Release Candidate</h2><p>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 <a shape="rect" href="testing-a-release-candidate.html">Testing a release candidate</a> guidelines.<br clear="none"> Afterwards send out the VOTE for this release can
didate to the dev@ mailing list.</p><h2 id="ReleaseGuide-AnnouncingtheCamelRelease">Announcing the Camel Release</h2><p>If the VOTE pass,</p><ol><li>Close it by sending the RESULT to the mailing list.</li><li>Promote the artifacts to the central repo. For this login to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a> 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.</li><li>Perform a <a shape="rect" class="external-link" href="https://issues.apache.org/jira/plugins/servlet/project-config/CAMEL/versions">release in JIRA</a> and create a new release versio
n in JIRA</li><li>There should be already a release notes page in the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/In+Progress">In Progress</a> folder (if not create one based on the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/Camel%20x.y.z%20Release%20(template)">Camel x.y.z Release (template)</a>). Edit it and change the number of fixed issues, and update its parent to be the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/Download">Download</a> page, and <strong>make sure</strong> 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.</li><li><p>Copy the newly deployed distribution to Apache website:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div></li><li>Close the staging repository<br clear="none"> Quote from the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">Maven release guide for Apache projects</a><blockquote><p>Login to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a> 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.</p></blockquote>See the screenshot below that shows the state of the
staging repository at this stage.<br clear="none"><br clear="none"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" height="250" src="release-guide.data/apache-nexus-close-repo.png" data-image-src="/confluence/download/attachments/68287/apache-nexus-close-repo.png?version=1&modificationDate=1448317837000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="61330078" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="apache-nexus-close-repo.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="68287" data-linked-resource-container-version="116"></span><br clear="none"><br clear="none"></li><li>Verify staged artifacts<br clear="none"> Quote from the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">o
riginal guide</a><blockquote><p>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.<br clear="none"> Note the repository URL, you will need this in your vote email.</p></blockquote></li></ol><h2 id="ReleaseGuide-TestingtheCamelReleaseCandidate">Testing the Camel Release Candidate</h2><p>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 <a shape="rect" href="testing-a-release-candidate.html">Testing a release candidate</a> guidelines.<br clear="none"> Afterwards send out the VOTE for this release can
didate to the dev@ mailing list.</p><h2 id="ReleaseGuide-AnnouncingtheCamelRelease">Announcing the Camel Release</h2><p>If the VOTE pass,</p><ol><li>Close it by sending the RESULT to the mailing list.</li><li>Promote the artifacts to the central repo. For this login to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a> 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.</li><li>Perform a <a shape="rect" class="external-link" href="https://issues.apache.org/jira/plugins/servlet/project-config/CAMEL/versions">release in JIRA</a> and create a new release versio
n in JIRA</li><li>There should be already a release notes page in the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/In+Progress">In Progress</a> folder (if not create one based on the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/Camel%20x.y.z%20Release%20(template)">Camel x.y.z Release (template)</a>). Edit it and change the number of fixed issues, and update its parent to be the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/Download">Download</a> page, and <strong>make sure</strong> 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.</li><li><p>Copy the newly deployed distribution to Apache website:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd ${CAMEL_ROOT_DIR}/etc/scripts
-release-distro.sh <Camel version>
+./release-distro.sh <Camel version>
]]></script>
-</div></div><p>Check the console output and finish this step (run svn ci) manually after checking the artifacts.</p></li><li>Remove the old release by using <span style="line-height: 1.4285715;">svn rm </span><a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/camel/apache-camel/2.13.0" style="line-height: 1.4285715;">https://dist.apache.org/repos/dist/release/camel/apache-camel/</a>OLD_CAMEL_VERSION<span style="line-height: 1.4285715;"> -m "Removed the old release"</span></li><li><span style="line-height: 1.4285715;">Update the download link of the <a shape="rect" href="camel-xyz-release-template.html">Camel x.y.z Release</a> to with <a shape="rect" class="external-link" href="http://archive.apache.org/dist/">http://archive.apache.org/dist/</a></span></li><li>Copy the KEYS file by ssh into /www/www.apache.org/dist/camel/apache-camel/ on people.apache.org <strong>if</strong> you changed it</li><li>Update the <a shape="rect" href
="https://cwiki.apache.org/confluence/display/CAMEL/Download">Download</a> page to refer to the latest release distributions (search & replace the version numbers mostly)</li><li><p>Upload the newly deployed schema and the manual to Apache:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The script will download all distribution artifacts using wget and eventually show the following message:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Distro artifacts prepared for upload, but not yet uploaded. Verify distro then complete upload!
+cd /tmp/camel-release/dist/x.y.z/
+svn status
+svn ci -m "Apache Camel x.y.z released artifacts."
+Remove previous distro on same branch if necessary
+DONE]]></script>
+</div></div><p>Finish this step by following the provided command sequence using svn after checking the artifacts.</p></li><li><p>Remove the old release by using <span style="line-height: 1.4285715;">svn:</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn rm https://dist.apache.org/repos/dist/release/camel/apache-camel/OLD_CAMEL_VERSION -m "Removed the old release"]]></script>
+</div></div></li><li><span style="line-height: 1.4285715;">Update the download link of the <a shape="rect" href="camel-xyz-release-template.html">Camel x.y.z Release</a> to with <a shape="rect" class="external-link" href="http://archive.apache.org/dist/">http://archive.apache.org/dist/</a></span></li><li>Copy the KEYS file by ssh into /www/www.apache.org/dist/camel/apache-camel/ on people.apache.org <strong>if</strong> you changed it</li><li>Update the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/Download">Download</a> page to refer to the latest release distributions (search & replace the version numbers mostly)</li><li><p>Upload the newly deployed schema and the manual to Apache:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd ${CAMEL_ROOT_DIR}/etc/scripts
-release-website.sh <Camel version>
+./release-website.sh <Camel version>
]]></script>
-</div></div><p>Check the console output and finish this step (run svn ci) manually after checking the artifacts.</p></li><li><p>Upload the javadocs to Apache, you need to checkout the files from "https://svn.apache.org/repos/infra/websites/production/camel/content/maven/"</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Using SVN the first time on people.apache.org</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>To be able to perform a checkout on people.apache.org from svn.apache.org, you have to trust the server certificate:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+</div></div><p>The script will download the website release artifacts using wget. Once all artifacts are downloaded, the following message is displayed:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[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"]]></script>
+</div></div><p>Finish this step by following the provided command sequence using svn after checking the artifacts.</p></li><li><p>Upload the javadocs to Apache, you need to checkout the files from "https://svn.apache.org/repos/infra/websites/production/camel/content/maven/"</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Using SVN the first time on people.apache.org</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>To be able to perform a checkout on people.apache.org from svn.apache.org, you have to trust the server certificate:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>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!
@@ -187,24 +211,7 @@ Certificate information:
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?
</pre>
-</div></div></div></div></li><li>Update the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/Xml+Reference">Xml Reference</a> page with a link to the XSD's</li><li>Update the <a shape="rect" href="manual.html">Manual</a> page with a link to the PDF/HTML <strong>if</strong> it's a new major/minor version</li><li>Mail the <a shape="rect" class="external-link" href="mailto:dev@camel.apache.org" rel="nofollow">dev@camel.apache.org</a>, <a shape="rect" class="external-link" href="mailto:users@camel.apache.org" rel="nofollow">users@camel.apache.org</a> & <a shape="rect" class="external-link" href="mailto:announce@apache.org" rel="nofollow">announce@apache.org</a> lists</li><li><a shape="rect" href="https://cwiki.apache.org/confluence/pages/createblogpost.action?spaceKey=CAMEL">Post</a> a news entry in the wiki which <strong>links to the release page</strong> so folks can download it!</li><li>perform a full export of the Camel WIKI sites to see your blog on the C
amel index site. To do this, you have to remove the main.pageCache file in the content/cache sub directory:<ol><li>execute: svn rm <a shape="rect" class="external-link" href="https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache">https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache</a></li></ol></li><li>Add the release version number to the following <code>spring.schemas</code> file located in <code>src/main/resources/META-INF</code> directory of the following components:<ul><li>camel-cxf (<a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-cxf/src/main/resources/META-INF/spring.schemas;hb=HEAD">/camel/components/camel-cxf/src/main/resources/META-INF/spring.schemas</a>)</li><li>camel-spring (<a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-spring/src/main/resources/META-
INF/spring.schemas;hb=HEAD">/camel/components/camel-spring/src/main/resources/META-INF/spring.schemas</a>)</li><li>camel-spring-integration (<a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-spring-integration/src/main/resources/META-INF/spring.schemas;hb=HEAD">/camel/components/camel-spring-integration/src/main/resources/META-INF/spring.schemas</a>)</li><li>camel-spring-security (<a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-spring-security/src/main/resources/META-INF/spring.schemas;hb=HEAD">/camel/components/camel-spring-security/src/main/resources/META-INF/spring.handlers</a>)</li></ul></li><li>Have a beer! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></li></ol><h2 id="Re
leaseGuide-Createanewmaintenancebranch">Create a new maintenance branch</h2><div class="confluence-information-macro confluence-information-macro-information"><p class="title">This section is out of date.</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>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.</p></div></div><p> </p><p>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.</p><ol><li><p>Create a branch from trunk remotely</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[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
-]]></script>
-</div></div></li></ol><ol><li><p>Check out the remote branch in a new directory</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn checkout https://svn.apache.org/repos/asf/camel/branches/camel-2.10.x
-]]></script>
-</div></div></li></ol><ol><li><p>Initialize merge tracking for the new branch</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[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
-]]></script>
-</div></div></li></ol><ol><li><p>Update the version number for the next patch release</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[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"
-]]></script>
-</div></div></li></ol><ol><li>Set up a new continuous integration build, if we release a new major/minor version: <a shape="rect" class="external-link" href="https://builds.apache.org/view/A-D/view/Camel/">https://builds.apache.org/view/A-D/view/Camel/</a></li></ol><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn release:clean -Prelease]]></script>
-</div></div></div>
+</div></div></div></div></li><li>Update the <a shape="rect" href="https://cwiki.apache.org/confluence/display/CAMEL/Xml+Reference">Xml Reference</a> page with a link to the XSD's</li><li>Update the <a shape="rect" href="manual.html">Manual</a> page with a link to the PDF/HTML <strong>if</strong> it's a new major/minor version</li><li>Mail the <a shape="rect" class="external-link" href="mailto:dev@camel.apache.org" rel="nofollow">dev@camel.apache.org</a>, <a shape="rect" class="external-link" href="mailto:users@camel.apache.org" rel="nofollow">users@camel.apache.org</a> & <a shape="rect" class="external-link" href="mailto:announce@apache.org" rel="nofollow">announce@apache.org</a> lists</li><li><a shape="rect" href="https://cwiki.apache.org/confluence/pages/createblogpost.action?spaceKey=CAMEL">Post</a> a news entry in the wiki which <strong>links to the release page</strong> so folks can download it!</li><li>perform a full export of the Camel WIKI sites to see your blog on the C
amel index site. To do this, you have to remove the main.pageCache file in the content/cache sub directory:<ol><li>execute: svn rm <a shape="rect" class="external-link" href="https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache">https://svn.apache.org/repos/infra/websites/production/camel/content/cache/main.pageCache</a></li></ol></li><li>Add the release version number to the following <code>spring.schemas</code> file located in <code>src/main/resources/META-INF</code> directory of the following components:<ul><li>camel-cxf (<a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-cxf/src/main/resources/META-INF/spring.schemas;hb=HEAD">/camel/components/camel-cxf/src/main/resources/META-INF/spring.schemas</a>)</li><li>camel-spring (<a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-spring/src/main/resources/META-
INF/spring.schemas;hb=HEAD">/camel/components/camel-spring/src/main/resources/META-INF/spring.schemas</a>)</li><li>camel-spring-integration (<a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-spring-integration/src/main/resources/META-INF/spring.schemas;hb=HEAD">/camel/components/camel-spring-integration/src/main/resources/META-INF/spring.schemas</a>)</li><li>camel-spring-security (<a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-spring-security/src/main/resources/META-INF/spring.schemas;hb=HEAD">/camel/components/camel-spring-security/src/main/resources/META-INF/spring.handlers</a>)</li></ul></li><li>Have a beer! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></li></ol></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/siteindex.html
==============================================================================
--- websites/production/camel/content/siteindex.html (original)
+++ websites/production/camel/content/siteindex.html Sun Sep 25 08:26:21 2016
@@ -524,7 +524,7 @@
<div class="smalltext" style="margin: 0 0 0 36px">Camel 2.16.3 Release http://camel.apache.org/images/camel-box-small.png New and Noteworthy Welcome to the 2.16.3 release which is mainly a maintenance release with voer 75 issues resolved. For further details, see the list of JIRA issues https://issues.a</div>
<span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="camel-2164-release.html">Camel 2.16.4 Release</a>
<br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Camel 2.16.4 Release (currently in progress) http://camel.apache.org/images/camel-box-small.png New and Noteworthy Welcome to the 2.16.4 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) highlighted issue fixe</div>
+ <div class="smalltext" style="margin: 0 0 0 36px">Camel 2.16.4 Release http://camel.apache.org/images/camel-box-small.png New and Noteworthy Welcome to the 2.16.4 release which is mainly a bug fix release with over 50 fixes and improvements. API breaking See Camel 2.16.0 Release http://camel.apache.org/</div>
<span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="camel-2170-release.html">Camel 2.17.0 Release</a>
<br clear="none">
<div class="smalltext" style="margin: 0 0 0 36px">Camel 2.17.0 Release http://camel.apache.org/download.data/camel-box-v1.0-150x200.png New and Noteworthy Welcome to the 2.17.0 release which resolved approx. 450 issues (new features, improvements and bug fixes). The component documentation generated fr</div>
@@ -984,7 +984,7 @@
<div class="smalltext" style="margin: 0 0 0 36px">Does Camel work on IBM's JDK? Yes, we've tested Camel with IBM's JDK on the AIX and Linux platforms. There are a few things to look out for though Exception using camel-http You may get a sun.io.MalformedInputException when using camel-http on IBM's JDK. </div>
<span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="download.html">Download</a>
<br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Latest Releases http://camel.apache.org/images/camel-box-small.png Grab these releases while they are hot! The latest release for Camel 2.17.x is Camel 2.17.3 Release. The latest release for Camel 2.16.x is Camel 2.16.3 Release. The latest release for Cam</div>
+ <div class="smalltext" style="margin: 0 0 0 36px">Latest Releases http://camel.apache.org/images/camel-box-small.png Grab these releases while they are hot! The latest release for Camel 2.17.x is Camel 2.17.3 Release. The latest release for Camel 2.16.x is Camel 2.16.4 Release. The latest release for Cam</div>
<span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="download-archives.html">Download Archives</a>
<br clear="none">
<div class="smalltext" style="margin: 0 0 0 36px">Download archives You can use the Apache Archives to download all the Camel releases. http://archive.apache.org/dist/camel/apache-camel/ http://archive.apache.org/dist/camel/apache-camel/ - All release since Camel became a top level Apache project http://</div>
@@ -1776,7 +1776,7 @@
<div class="smalltext" style="margin: 0 0 0 36px">Camel In your pom.xml file you can add the Maven 2 snapshot repository if you want to try out the xxx-SNAPSHOT versions: <repository> <id>apache.snapshots</id> <name>Apache Development Snapshot Repository</name> <url>https://repository.apache.org/content/</div>
<span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="mdc-logging.html">MDC logging</a>
<br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">MDC logging Available as of Camel 2.7 In Camel 2.7 we migrated to use slf4j http://www.slf4j.org/ as the logging framework in Camel. This allows us to support MDC logging http://www.slf4j.org/api/org/slf4j/MDC.html. See more details about MDC logging in t</div>
+ <div class="smalltext" style="margin: 0 0 0 36px">MDC logging Available as of Camel 2.7 From Camel 2.7: Camel uses the SLF4J http://www.slf4j.org/ logging framework. This allows Camel to support MDC logging http://www.slf4j.org/api/org/slf4j/MDC.html. For more information about about MDC logging see the </div>
<span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="memory-leak-when-adding-and-removing-routes-at-runtime.html">Memory leak when adding and removing routes at runtime</a>
<br clear="none">
<div class="smalltext" style="margin: 0 0 0 36px">Memory leak when adding and removing routes at runtime If you add and remove many routes at runtime, then take notice that JMX may take up memory when routes is added. As Camel cannot 100% reclaim all mbeans when removing a route (some resources may be sh</div>