Author: buildbot
Date: Fri Mar 8 06:27:31 2013
New Revision: 853594
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/contributing.html
Modified: websites/production/camel/content/contributing.html
==============================================================================
--- websites/production/camel/content/contributing.html (original)
+++ websites/production/camel/content/contributing.html Fri Mar 8 06:27:31 2013
@@ -107,10 +107,12 @@
<p>Please raise a new issue in our <a shape="rect" class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue tracker</a></p>
+
<p>If you can create a JUnit test case then your issue is more likely to be
resolved quicker.<br clear="none">
e.g. take a look at some of the existing <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/";>unit
tests cases</a></p>
+
<p>Then we can add your issue to Subversion and then we'll know when its
really fixed and we can ensure that the problem stays fixed in future
releases.</p>
<h2><a shape="rect" name="Contributing-Workingonthecode"></a>Working on the
code</h2>
@@ -171,14 +173,14 @@ svn diff Main.java >> patchfile.tx
<p>The minor "problem" is creating the local repository connected to the
official repository. Next step is modifying the codebase. The major "problem"
then is getting the modifications back to the official ASF repository.<br
clear="none">
-Depending on the chosen way these steps differ which is short described here.
</p>
+Depending on the chosen way these steps differ which is short described
here.</p>
<h3><a shape="rect" name="Contributing-gitsvn"></a>git-svn</h3>
<p>With Git you cannot fork another Git repository - you also could "fork" a
subversion repository.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
-git svn clone https:<span
class="code-comment">//svn.apache.org/repos/asf/camel/trunk
<TargetDirectory> </span>
+git svn clone https:<span
class="code-comment">//svn.apache.org/repos/asf/camel/trunk
<TargetDirectory></span>
</pre>
</div></div>
@@ -201,7 +203,7 @@ git format-patch origin/trunk
<p>Forking the Git repo from here is much smoother, because you are forking a
"real" Git repo.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
-git fork git:<span class="code-comment">//git.apache.org/camel.git
<TargetDirectory> </span>
+git fork git:<span class="code-comment">//git.apache.org/camel.git
<TargetDirectory></span>
</pre>
</div></div>
@@ -211,14 +213,14 @@ git fork git:<span class="code-comment">
<h3><a shape="rect" name="Contributing-PullrequestatGithub"></a>Pull request
at Github</h3>
-<p>There is also a Git <a shape="rect" class="external-link"
href="https://github.com/apache/camel"; rel="nofollow">repository at Github</a>
which you could fork. Then you work on a new feature branch and send a pull
request. For granting the license you also should create a Jira issue with a
reference to that pull request. One of the committers then could bring that
changesets to the ASF codebase via his/her own local repository. After closing
the Jira issue you have to close the pull request because we can't do that...
</p>
+<p>There is also a Git <a shape="rect" class="external-link"
href="https://github.com/apache/camel"; rel="nofollow">repository at Github</a>
which you could fork. Then you work on a new feature branch and send a pull
request. For granting the license you also should create a Jira issue with a
reference to that pull request. One of the committers then could bring that
changesets to the ASF codebase via his/her own local repository. After closing
the Jira issue you have to close the pull request because we can't do
that...</p>
<p>Same drawback here - it is one day behind ...</p>
<h3><a shape="rect" name="Contributing-Moreresources"></a>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/general/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>
+<ul><li><a shape="rect" class="external-link"
href="http://wiki.apache.org/general/GitAtApache";>http://wiki.apache.org/general/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><a shape="rect" name="Contributing-Becomingacommitter"></a>Becoming a
committer</h2>
