Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of cutting@gmail.com designates
 209.85.198.229 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:message-id:date:from:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=FT9DrR9mD9qgn/5V6AhVgK4HHfYGIq5eA4mnTfhyDSDf35CdabPrF+EHUvNcLWTaff
         mNdeZDhc7l7L6fe8WXPu3ldFaX1fCKmDYi9AnZzL7reHt1Z+Ip5odbm0mk3DmquZH1fd
         uLkJ3I6b8xPuleD64cF9lKYe4I2JrEVsI5GfI=
Sender: Doug Cutting <cutting@gmail.com>
Message-ID: <499CA09B.3060800@apache.org>
Date: Wed, 18 Feb 2009 15:58:19 -0800
From: Doug Cutting <cutting@apache.org>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: core-dev@hadoop.apache.org
Subject: Re: Hadoop 0.19.1
References: 
 <4AB0C5D9593B434CB25AFEE43248EC99027DBF@SNV-EXVS05.ds.corp.yahoo.com>
 <4999931C.4050309@apache.org>
In-Reply-To: <4999931C.4050309@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Steve Loughran wrote:
> One thing about Git is that it has a more laid back notion of what is 
> "trunk"; you'd end up with more a blurred distro, with -maybe- the Y! 
> production scheme, the Cloudera branch, the steves-modified-branch, etc, 
> etc -with people able to pick and choose which to merge in. There's less 
> of a trunk+branches, more just a set of branches.

Yes, but trunk is what we share as a community, our consensus reality. 
We should be careful not to overly fragment our community.  We can't 
vote on a blurred release.  The ASF development style will change, 
better embracing tools like Git, but we should change it slowly and 
cautiously lest we lose what we value.

Doug