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/11/12 08:20:14 UTC
svn commit: r1001010 - in /websites/production/camel/content:
cache/main.pageCache release-guide.html
Author: buildbot
Date: Sat Nov 12 08:20:14 2016
New Revision: 1001010
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/release-guide.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/release-guide.html
==============================================================================
--- websites/production/camel/content/release-guide.html (original)
+++ websites/production/camel/content/release-guide.html Sat Nov 12 08:20:14 2016
@@ -86,7 +86,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1 id="ReleaseGuide-HowtocreateandannounceaCamelrelease.">How to create and announce a Camel release.</h1><p>This release guide is based on the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">General guide for releasing Maven-based projects at Apache</a>, so be sure to check it out before continuing and meet all prerequisites.</p><p><span style="font-size: 20.0px;line-height: 1.5;">Prerequisites</span></p><p>To prepare or perform a release you MUST BE at least an Apache Camel committer.</p><ul><li>The artifacts for each and every release must be SIGNED; your public key should be added to the KEYS file</li><li>Your public key must also be cross-signed by other Apache committers (this can be done at key signing parties at ApacheCon for instance)</li><li>Make sure you have the correct maven configuration in <code>~/.m2/settings.xml</code></li><li>From Camel 2.10 onwards we will require to
use Maven [3.0.2,3.1.0)</li><li>From Camel 2.11 onwards we will require to use Maven [3.0.4,3.1.0]</li><li>From Camel 2.15 onwards we will require to use Maven [3.1.1,3.2.5)</li><li>You may want to get familiar with the release settings in the parent apache POM.</li><li>Make sure you are using Java 1.7 for Apache Camel 2.14.0 and later (Java 1.6 for older versions).<br clear="none"><br clear="none"></li></ul><h2 id="ReleaseGuide-Maven2Setup">Maven 2 Setup</h2><p>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 <a shape="rect" class="external-link" href="http://maven.apache.org/developers/committer-settings.html">guidelines </a> used by the Maven project. Please pay particular attention to the <a shape="rect" c
lass="external-link" href="http://maven.apache.org/guides/mini/guide-encryption.html">password encryption recommendations</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h1 id="ReleaseGuide-HowtocreateandannounceaCamelrelease.">How to create and announce a Camel release.</h1><p>This release guide is based on the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">General guide for releasing Maven-based projects at Apache</a>, so be sure to check it out before continuing and meet all prerequisites.</p><p><span style="font-size: 20.0px;line-height: 1.5;">Prerequisites</span></p><p>To prepare or perform a release you MUST BE at least an Apache Camel committer.</p><ul><li>The artifacts for each and every release must be SIGNED; your public key should be added to the KEYS file</li><li>Your public key must also be cross-signed by other Apache committers (this can be done at key signing parties at ApacheCon for instance)</li><li>Make sure you have the correct maven configuration in <code>~/.m2/settings.xml</code></li><li>From Camel 2.15 onwards we will require to
use Maven [3.1.1,3.2.5)</li><li>From Camel 2.17 onwards we will require to use Maven [3.2.5,3.3.x)</li><li>You may want to get familiar with the release settings in the parent apache POM.</li><li>Make sure you are using Java 1.8 for Apache Camel 2.18.0 and later (Java 1.7 for older versions).<br clear="none"><br clear="none"></li></ul><h2 id="ReleaseGuide-Maven2Setup">Maven 2 Setup</h2><p>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 <a shape="rect" class="external-link" href="http://maven.apache.org/developers/committer-settings.html">guidelines </a> used by the Maven project. Please pay particular attention to the <a shape="rect" class="external-link" href="http://maven.apache.org/guides/mini/guide-encryp
tion.html">password encryption recommendations</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<settings>
...
<servers>
@@ -169,7 +169,7 @@ 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="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">
+</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="117"></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>
]]></script>