Author: buildbot
Date: Mon Feb 6 09:18:40 2017
New Revision: 1006291
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/contributing.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/contributing.html
==============================================================================
--- websites/production/camel/content/contributing.html (original)
+++ websites/production/camel/content/contributing.html Mon Feb 6 09:18:40 2017
@@ -107,7 +107,7 @@ cd camel
</div></div><p>or</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[git diff --no-prefix > patchfile.txt
]]></script>
-</div></div><h2 id="Contributing-Submittingpatches">Submitting
patches</h2><p>The easiest way to submit a patch is to</p><ul><li><a
shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CAMEL";>create a new JIRA issue</a>
(you will need to register),</li><li>attach the patch or tarball as an
attachment (if you create a patch file, but we recommend using github
PRs)</li><li><strong>tick the Patch Attached</strong> button on the
issue</li></ul><p>We prefer patches has unit tests as well and that these unit
tests have proper assertions as well, so remember to replace your system.out or
logging with an assertion instead!</p><h3 id="Contributing-Moreresources">More
resources</h3><p>Git is not a brand new technology and therefore Camel is not
the only ASF project thinking about using it. So here are some more resources
you mind find useful:</p><ul><li><a shape="rect" class="external-link"
href="http://wiki.apache.org/general/GitAtApache";>http://wiki.apache.org/gene
ral/GitAtApache</a>: Some basic notes about git@asf</li><li><a shape="rect"
class="external-link" href="http://git.apache.org/";>http://git.apache.org/</a>:
List of mgit-mirrors at ASF</li><li><a shape="rect" class="external-link"
href="https://git-wip-us.apache.org/";>https://git-wip-us.apache.org/</a>: More
Git infos from Apache</li></ul><h2
id="Contributing-Becomingacommitter">Becoming a committer</h2><p>Once you've
got involved as above, we may well invite you to be a committer. See <a
shape="rect" href="how-do-i-become-a-committer.html">How do I become a
committer</a> for more details.</p><h2
id="Contributing-Usingtheissuetracker">Using the issue tracker</h2><p>Before
you can raise an issue in the <a shape="rect" class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue tracker</a> you
need to register with it. This is quick & painless.</p><p>If you want to
have a go at fixing an issue you need to be in the list of camel-developers on
the issue tracker
. To join the group, please mail the <code>d...@camel.apache.org</code> mail
list with the email address you used to register with the issue tracker and
we'll add you to the group.</p><h2
id="Contributing-Becomingacommitter.1">Becoming a committer</h2><p>The first
step is contributing to the project; if you want to take that a step forward
and become a fellow committer on the project then see the <a shape="rect"
class="external-link"
href="http://activemq.apache.org/becoming-a-committer.html";>Committer
Guide</a></p></div>
+</div></div><h2 id="Contributing-Submittingpatches">Submitting
patches</h2><p>The easiest way to submit a patch is to</p><ul><li><a
shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CAMEL";>create a new JIRA issue</a>
(you will need to register),</li><li>attach the patch or tarball as an
attachment (if you create a patch file, but we recommend using github
PRs)</li><li><strong>tick the Patch Attached</strong> button on the
issue</li></ul><p>We prefer patches has unit tests as well and that these unit
tests have proper assertions as well, so remember to replace your system.out or
logging with an assertion instead!</p><h3 id="Contributing-Moreresources">More
resources</h3><p>Git is not a brand new technology and therefore Camel is not
the only ASF project thinking about using it. So here are some more resources
you mind find useful:</p><ul><li><a shape="rect" class="external-link"
href="http://wiki.apache.org/general/GitAtApache";>http://wiki.apache.org/gene
ral/GitAtApache</a>: Some basic notes about git@asf</li><li><a shape="rect"
class="external-link" href="http://git.apache.org/";>http://git.apache.org/</a>:
List of mgit-mirrors at ASF</li><li><a shape="rect" class="external-link"
href="https://git-wip-us.apache.org/";>https://git-wip-us.apache.org/</a>: More
Git infos from Apache</li></ul><h2
id="Contributing-Becomingacommitter">Becoming a committer</h2><p>Once you've
got involved as above, we may well invite you to be a committer. See <a
shape="rect" href="how-do-i-become-a-committer.html">How do I become a
committer</a> for more details.</p><h2
id="Contributing-Usingtheissuetracker">Using the issue tracker</h2><p>Before
you can raise an issue in the <a shape="rect" class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue tracker</a> you
need to register with it. This is quick & painless.</p><h2
id="Contributing-Becomingacommitter.1">Becoming a committer</h2><p>The first
step is contributing to the proje
ct; if you want to take that a step forward and become a fellow committer on
the project then see the <a shape="rect" class="external-link"
href="http://activemq.apache.org/becoming-a-committer.html";>Committer
Guide</a></p></div>
</td>
<td valign="top">
<div class="navigation">
