Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of mbhandarkar@linkedin.com
 designates 69.28.149.25 as permitted sender)
DomainKey-Signature: s=prod; d=linkedin.com; c=nofws; q=dns;
  h=X-IronPort-AV:Received:From:To:CC:Subject:Thread-Topic:
   Thread-Index:Date:Message-ID:In-Reply-To:Accept-Language:
   Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:
   x-originating-ip:Content-Type:Content-ID:
   Content-Transfer-Encoding:MIME-Version;
  b=pamtRap3GtJk1lWhPrldiCY3kGnGgm2zyCyywCoUbi2ye8MYRJdljY/Q
   6pYIyDJ3aND/62ITN2n99lDIxV0JyoiR0U1ubDrT/dhHeV7yBbYA8bSgH
   i9vf472a9CDyzOe;
From: Milind Bhandarkar <mbhandarkar@linkedin.com>
To: "general@hadoop.apache.org" <general@hadoop.apache.org>
CC: Steve Loughran <stevel@apache.org>
Subject: Re: [DISCUSSION] development process of Hadoop
Thread-Topic: [DISCUSSION] development process of Hadoop
Thread-Index: 
 AQHMCwoF5EVOIXU1nkuwTbIZGN61ApR+kEyAgABjsgCAAAWnAIABPG0AgAAZjYD//7UFgA==
Date: Fri, 6 May 2011 16:51:28 +0000
Message-ID: <C9E973E8.8664%mbhandarkar@linkedin.com>
In-Reply-To: <4DC402B7.8070900@uci.cu>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5B9BCCFB9CF6524695285BCB4425F578@linkedin.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

+1 for git.

When (not if) Apache Hadoop switches to git, I would recommend all to
consider the branching model beautifully described in
http://nvie.com/posts/a-successful-git-branching-model/.

- milind

--=20
Milind Bhandarkar
mbhandarkar@linkedin.com
+1-650-776-3167


On 5/6/11 7:16 AM, "Marcos Ortiz" <mlortiz@uci.cu> wrote:

>On 05/06/2011 08:14 AM, Steve Loughran wrote:
>> On 05/05/11 18:52, Todd Lipcon wrote:
>>> On Thu, May 5, 2011 at 10:32 AM, Eric Yang<eyang@yahoo-inc.com>  wrote:
>>>
>>>> Git is powerful in maintaining different branch of the source code.
>>>>   However, it will only work if the entire community is willing to
>>>> move to
>>>> git.  Maintaining svn and git hybrid, is a time consuming task that
>>>> we are
>>>> paying in full price.  Hadoop community should work smarter for the
>>>> source
>>>> control.  What do people think about fully adopting git instead of
>>>>svn?
>>>>
>>>
>>> +1 for Git as a tool. But using git makes it even _more_ important
>>> that we
>>> have a clearly defined release process that outlines which branches are
>>> meant to be released as official artifacts, and what the inclusion
>>> criteria
>>> for those branches should be.
>>>
>>
>> I'm +0.9995 for git: some bits I like, some bits I don't (it's awful
>> for binary data). And you need more than just a release process locked
>> down, you need the developers understanding following a good process.
>> If you have written down process docs there, I'd love to see them.
>>
>> apache infrastructure are discussing git -what would be best would be
>> to start with a non-critical project, such as one or more of the moved
>> contrib projects (like MR-Unit), so we can see that it, gerrit, etc
>> work well within the Hadoop developer world.
>>
>>
>>
>+1 for Git
>
>We migrated from SVN to Git for our completed infrastructure, for many
>reason:
>- Git use much less space than SVN, all the changes are in a single .git
>- Git is awesome for branching
>- Another great advantage is that there are many developers that know
>Git, and how the development process can be greatly improved.
>
>PostgreSQL, one of my favorites open source projects that I use on my
>daily work, migrated the development process to Git from CVS.
>
>Regards.
>
>--=20
>Marcos Lu=EDs Ort=EDz Valmaseda
>  Software Engineer (Large-Scaled Distributed Systems)
>  University of Information Sciences,
>  La Habana, Cuba
>  Linux User # 418229
>  http://about.me/marcosortiz
>