Author: buildbot
Date: Thu Mar 21 15:34:19 2013
New Revision: 855438
Log:
Staging update by buildbot for cloudstack
Modified:
websites/staging/cloudstack/trunk/content/ (props changed)
websites/staging/cloudstack/trunk/content/develop/environment.html
websites/staging/cloudstack/trunk/content/develop/non-contributors.html
Propchange: websites/staging/cloudstack/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 21 15:34:19 2013
@@ -1 +1 @@
-1459354
+1459362
Modified: websites/staging/cloudstack/trunk/content/develop/environment.html
==============================================================================
--- websites/staging/cloudstack/trunk/content/develop/environment.html
(original)
+++ websites/staging/cloudstack/trunk/content/develop/environment.html Thu Mar
21 15:34:19 2013
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
- <title>Setting Up an Apache CloudStack (Incubating) Development
Environment</title>
+ <title>Setting Up an Apache CloudStack Development Environment</title>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
@@ -117,7 +117,7 @@
<p>Want to set up an Apache CloudStack development environment? We'll show you
how to set up a development environment under Linux with Eclipse as the IDE. Be
sure to check the <a href="#maven">new Maven instructions for major releases
after CloudStack 4.0.0-incubating.</a></p>
<h2 id="getting-source">Getting Source</h2>
<p>CloudStack uses git for source version control, if you know little about
git, http://book.git-scm.com/ is a good start. Once you have git setup on your
machine, pull source with:</p>
-<div class="codehilite"><pre><span class="n">git</span> <span
class="n">clone</span> <span class="n">https:</span><span
class="sr">//gi</span><span class="n">t</span><span class="o">-</span><span
class="n">wip</span><span class="o">-</span><span class="n">us</span><span
class="o">.</span><span class="n">apache</span><span class="o">.</span><span
class="n">org</span><span class="sr">/repos/</span><span
class="n">asf</span><span class="o">/</span><span
class="n">incubator</span><span class="o">-</span><span
class="n">cloudstack</span><span class="o">.</span><span class="n">git</span>
+<div class="codehilite"><pre><span class="n">git</span> <span
class="n">clone</span> <span class="n">https:</span><span
class="sr">//gi</span><span class="n">t</span><span class="o">-</span><span
class="n">wip</span><span class="o">-</span><span class="n">us</span><span
class="o">.</span><span class="n">apache</span><span class="o">.</span><span
class="n">org</span><span class="sr">/repos/</span><span
class="n">asf</span><span class="o">/</span><span
class="n">cloudstack</span><span class="o">.</span><span class="n">git</span>
</pre></div>
Modified:
websites/staging/cloudstack/trunk/content/develop/non-contributors.html
==============================================================================
--- websites/staging/cloudstack/trunk/content/develop/non-contributors.html
(original)
+++ websites/staging/cloudstack/trunk/content/develop/non-contributors.html Thu
Mar 21 15:34:19 2013
@@ -114,7 +114,7 @@
</div>
<div class="span9">
<p> <h1
id="contributing-to-apache-cloudstack-as-a-non-committer">Contributing to
Apache CloudStack as a Non-Committer</h1>
-<p>If you're a committer on an Apache project, it means that you can commit
directly to the project's repository. For instance, with Apache CloudStack
(incubating) committers are allowed to directly push commits into the git
repository. </p>
+<p>If you're a committer on an Apache project, it means that you can commit
directly to the project's repository. For instance, with Apache CloudStack
committers are allowed to directly push commits into the git repository. </p>
<p>Non-committers, however, have to submit patches for review. Don't worry,
it's not an onerous process at all. The first time you submit a patch, it will
take a minute or two to create an account on <a
href="http://reviews.apache.org/";>Review Board</a>, but it's a piece of cake
from start to finish.</p>
<h2 id="assumptions">Assumptions</h2>
<p>For the purpose of this post, we'll assume that you already have a system
with <a href="http://git-scm.com/";>Git</a> and have found a bug to fix or have
a feature that you'd like to submit, and you're willing to contribute that code
or documentation under the <a
href="http://www.apache.org/licenses/LICENSE-2.0.html";>Apache License
2.0</a>.</p>
@@ -126,13 +126,13 @@
<p><code>git config --global user.name "Your Name"</code></p>
<p><code>git config --global user.email y...@domain.com</code></p>
<p>You'll grab the CloudStack source with git:</p>
-<p><code>$ git clone
https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git</code></p>
+<p><code>$ git clone
https://git-wip-us.apache.org/repos/asf/cloudstack.git</code></p>
<p>If you already have the source, make sure you're working with the most
recent version. Do a <code>git pull</code> if you cloned the source more than a
few hours ago. (Apache CloudStack development can move pretty fast!) </p>
<p>Now that you have an up-to-date copy of the source, create a branch to do
your work in:</p>
<p><code>$ git checkout -b mybranch</code></p>
<p>This does two things: One, it creates the branch <em>mybranch</em> and two,
it changes your working branch to <em>mybranch</em>. Running <code>git
branch</code> will show you which branch you're working on, with an asterisk
next to the active branch, like so:</p>
<pre>
-[user@localhost incubator-cloudstack]$ git branch
+[user@localhost cloudstack]$ git branch
master
* mybranch
</pre>
