hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jay Booth <jaybo...@gmail.com>
Subject Re: [DISCUSS] Move project split down a level
Date Fri, 14 Jan 2011 19:59:28 GMT
On the flipside, right now it's only the developers, QAs and release
engineers.  There hasn't been much movement to 0.21 yet, and if we're agreed
on the change in general, then pushing out 0.22 without it means making
users change everything twice.

On Fri, Jan 14, 2011 at 2:53 PM, Tsz Wo (Nicholas), Sze <
s29752-hadoopgeneral@yahoo.com> wrote:

> This is a kind of an incompatible change: all the developers, QAs, release
> engineers and users have to change their local settings and scripts for
> this
> change.  Moreover, there are documentations, web pages and existing tools
> using
> the Apache svn URLs.  So it is a huge impact.  I am conservative on this
> since,
> as Konstantin mentioned, we risk to get into the same mess, and it will
> create
> more work for the community.
>
> Why do we want to enforce the releases as a unit, given that the long term
> target is to release these 3 projects independently?
>
> Nicholas
>
>
>
>
>
> ________________________________
> From: Nigel Daley <ndaley@mac.com>
> To: general@hadoop.apache.org
> Sent: Fri, January 14, 2011 11:21:25 AM
> Subject: Re: [DISCUSS] Move project split down a level
>
>
> On Jan 14, 2011, at 11:16 AM, Tsz Wo (Nicholas), Sze wrote:
>
> > Hi Nigel,
> >
> >> As I look more at the impact of the common/MR/HDFS project split on what
> >> and how we release Hadoop, I feel like the split needs an adjustment.
>  Many
> >> folks I've talked to agree that the project split has caused us a
> splitting
> >> headache.  I think 1 relatively small change could alleviate some of
> that.
> >
> > Could you elaborate your idea on how the proposed changes would help?
>  What the
> >
> > problems are being addressed?  It is not clear to me.
>
> Critical in my mind was my statement: "We're a long way from releasing
> these 3
> projects independently.  Given that, they should be branched and released
> as a
> unit."  This can not be enforced given the current svn layout. Other's can
> weigh
> in with additional thoughts.
>
> > You are right that the change is small but the impact is huge.  We should
> first
> >
> > understand what we are getting from the changes before doing it.
>
> What do you see as the huge impact?
>
> Nige
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message