Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of tom.e.white@gmail.com
 designates 209.85.216.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=trbwTGGNgVUn6X3Qm23iRgE09iOHTvQ0svwOUsfso+/cEEsTbbNKNVIxUtRTsnDUJ8
         n1t8zXUkc83T4fNHg7BwzLAl0b6coWhpWI0+W1dEMd9fPoox9RT7ADLoCYO8Fq+prfpx
         WsZXCPceEy2c3r4qRKIl5/GZXZxd5qRUrv8BU=
MIME-Version: 1.0
In-Reply-To: <AANLkTimYUTULEMpiNfNCvqv604JqMeR7a4AdXivxvfic@mail.gmail.com>
References: <D1B0544A-E594-4530-BAEA-46EFFE97676A@mac.com>
 <4A1492FF-C4B5-4949-B197-53B3A3B1BE29@apache.org>
 <AANLkTimYUTULEMpiNfNCvqv604JqMeR7a4AdXivxvfic@mail.gmail.com>
From: Tom White <tom.e.white@gmail.com>
Date: Fri, 14 Jan 2011 09:35:45 -0800
Message-ID: <AANLkTi=WA5aXiK2hZ58ysvQ0md1aP4NNmj+2T7b3mKej@mail.gmail.com>
Subject: Re: [DISCUSS] Move project split down a level
To: general@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1 to Owen's modified layout.

The current layout means that every svn operation made during a
release has to be carried out three times which increases the amount
of work and the chances of a mistake.

Cheers
Tom

On Fri, Jan 14, 2011 at 9:17 AM, Todd Lipcon <todd@cloudera.com> wrote:
> On Fri, Jan 14, 2011 at 8:51 AM, Owen O'Malley <omalley@apache.org> wrote=
:
>
>>
>> On Jan 13, 2011, at 10:18 PM, Nigel Daley wrote:
>>
>> =A0Folks,
>>>
>>> As I look more at the impact of the common/MR/HDFS project split on wha=
t
>>> and how we release Hadoop, I feel like the split needs an adjustment. =
=A0Many
>>> folks I've talked to agree that the project split has caused us a split=
ting
>>> headache. =A0I think 1 relatively small change could alleviate some of =
that.
>>>
>>> CURRENT SVN REPO:
>>>
>>> hadoop / [common, mapreduce, hdfs] / trunk
>>> hadoop / [common, mapreduce, hdfs] / branches
>>>
>>> PROPOSAL:
>>>
>>> hadoop / trunk / [common, mapreduce, hdfs]
>>> hadoop / branches / [common, mapreduce, hdfs]
>>>
>>
>>
>> Moving the source trees back together is ok, but will cause a fair amoun=
t
>> of churn for those of us that depend on the git versions of the reposito=
ry.
>> Using Todd's hack may be able to fix it again at least for each individu=
al
>> user.
>>
>
> Yep, I think we can set this up in a reasonable way with grafts. I'm happ=
y
> to write a little shell script we can put on the wiki for git users that
> would make the history look sane.
>
> Depending on how the git mirrors work, we might even be able to get the
> official git.apache.org one to work, too. If we decide to go forward with
> this plan I'll talk to the relevant INFRA folks and see about that.
>
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera
>