Return-Path: X-Original-To: apmail-cloudstack-commits-archive@www.apache.org Delivered-To: apmail-cloudstack-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2C660F51E for ; Thu, 21 Mar 2013 15:34:42 +0000 (UTC) Received: (qmail 4145 invoked by uid 500); 21 Mar 2013 15:34:42 -0000 Delivered-To: apmail-cloudstack-commits-archive@cloudstack.apache.org Received: (qmail 4127 invoked by uid 500); 21 Mar 2013 15:34:42 -0000 Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list commits@cloudstack.apache.org Received: (qmail 4120 invoked by uid 99); 21 Mar 2013 15:34:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Mar 2013 15:34:42 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Mar 2013 15:34:40 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 4B46723889D7 for ; Thu, 21 Mar 2013 15:34:20 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r855438 - in /websites/staging/cloudstack/trunk/content: ./ develop/environment.html develop/non-contributors.html Date: Thu, 21 Mar 2013 15:34:20 -0000 To: commits@cloudstack.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20130321153420.4B46723889D7@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org 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 @@ - Setting Up an Apache CloudStack (Incubating) Development Environment + Setting Up an Apache CloudStack Development Environment @@ -117,7 +117,7 @@

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 new Maven instructions for major releases after CloudStack 4.0.0-incubating.

Getting Source

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:

-
git clone https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
+
git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git
 
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 @@

Contributing to Apache CloudStack as a Non-Committer

-

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.

+

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.

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 Review Board, but it's a piece of cake from start to finish.

Assumptions

For the purpose of this post, we'll assume that you already have a system with Git 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 Apache License 2.0.

@@ -126,13 +126,13 @@

git config --global user.name "Your Name"

git config --global user.email you@domain.com

You'll grab the CloudStack source with git:

-

$ git clone https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git

+

$ git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git

If you already have the source, make sure you're working with the most recent version. Do a git pull if you cloned the source more than a few hours ago. (Apache CloudStack development can move pretty fast!)

Now that you have an up-to-date copy of the source, create a branch to do your work in:

$ git checkout -b mybranch

This does two things: One, it creates the branch mybranch and two, it changes your working branch to mybranch. Running git branch will show you which branch you're working on, with an asterisk next to the active branch, like so:

-[user@localhost incubator-cloudstack]$ git branch
+[user@localhost cloudstack]$ git branch
   master
 * mybranch