Author: buildbot
Date: Sun Nov 22 16:18:55 2015
New Revision: 973231
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 Sun Nov 22 16:18:55
2015
@@ -167,7 +167,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
]]></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 image in the original guide for more
info.</l
i><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";>original
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 candidate to the dev@ mailing list.</p><h2
id="ReleaseGuide-Manuallyupdatingfiles">Manually updating files</h2><p>From
camel 2.14.x, you don't need to update the  pom version of the below
modules if you already specify the -Prelease in the mvn release:xxx
command.</p><p>The <code>pom.xml</code> files in <code>etc</code>,
<code>tests/camel-itest-karaf</code>, <code>tests/camel-itest-osgi</code>,
<code>tests/camel-itest-performance</code> and
<code>tests/camel-performance</code> need to be manually updated with the Camel
version number in the <code><parent></code> tag.</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 shap
e="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 version in JIRA</li><li>There should be
already a release notes page in the <a shape="rect" href="in-progress.html">In
Progress</a> folder (if not create one based on the <a shape="rect"
href="camel-xyz-release-template.html">Camel x.y.z Release (template)</a>).
Edit it and change t
he number of fixed issues, and update its parent to be the <a shape="rect"
href="download.html">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 image in the original guide for more
info.</l
i><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";>original
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 candidate to the dev@ mailing list.</p><h2
id="ReleaseGuide-Manuallyupdatingfiles">Manually updating files</h2><p>From
camel 2.14.x, you don't need to update the  pom version of the below
modules if you already specify the -Prelease in the mvn release:xxx
command.</p><p>The <code>pom.xml</code> files in <code>etc</code>,
<code>tests/camel-itest-karaf</code>, <code>tests/camel-itest-osgi</code>,
<code>tests/camel-itest-performance</code> and
<code>tests/camel-performance</code> need to be manually updated with the Camel
version number in the <code><parent></code> tag.</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 shap
e="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 version 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/C
AMEL/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>
