Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A944AE458 for ; Wed, 2 Jan 2013 17:50:50 +0000 (UTC) Received: (qmail 45487 invoked by uid 500); 2 Jan 2013 17:50:50 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 45451 invoked by uid 500); 2 Jan 2013 17:50:50 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 45442 invoked by uid 99); 2 Jan 2013 17:50:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 17:50:50 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rohit.yadav@citrix.com designates 203.166.19.134 as permitted sender) Received: from [203.166.19.134] (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 17:50:45 +0000 X-IronPort-AV: E=Sophos;i="4.84,397,1355097600"; d="scan'208";a="248361" Received: from banpmailmx02.citrite.net ([10.103.128.74]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 02 Jan 2013 17:50:22 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.72]) by BANPMAILMX02.citrite.net ([10.103.128.74]) with mapi; Wed, 2 Jan 2013 23:20:20 +0530 From: Rohit Yadav To: "cloudstack-dev@incubator.apache.org" Date: Wed, 2 Jan 2013 23:16:10 +0530 Subject: RE: Private development branch Thread-Topic: Private development branch Thread-Index: Ac3pCGlqldMZfvomQIepuicHHHFaRwACKPDm Message-ID: <0BCCCE152323764BB7FD6AE6D7A1D9060102894ED02C@BANPMAILBOX01.citrite.net> References: <35F04D4C394874409D9BE4BF45AC5EA9010B2854B818@BANPMAILBOX01.citrite.net>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org There are a lot of forks [1] where people do private or experimental develo= pment by creating their remote branches. You can also have private git bran= ch on github or if you setup your own git server on a vps or whatnot. Regards. [1] https://github.com/apache/incubator-cloudstack/network/members ________________________________________ From: David Nalley [david@gnsa.us] Sent: Wednesday, January 02, 2013 10:13 PM To: cloudstack-dev@incubator.apache.org Subject: Re: Private development branch On Wed, Jan 2, 2013 at 4:26 AM, Sateesh Chodapuneedi wrote: > Hi, > I think the current work flow for development (non-committer) fits well f= or small patch development. > But in case of feature development or bigger patches which might need lon= ger period of development, developer need some place to push the code chang= es. It's needed to push code changes to secure location rather than depend = on commits to local repository (in their development machine). > > Would forking ASFCS on any public git host (github.com) sound good? Is th= at a legitimate idea? > > Regards, > Sateesh While I don't like the term 'private' I think it's fine to use github or some similar service for this purpose. If you do use github, forking our github mirror[1] is probably easiest. [1] https://github.com/apache/incubator-cloudstack