On Fri, Feb 11, 2011 at 9:04 AM, Eric Sammer <esam...@cloudera.com> wrote:
> On Fri, Feb 11, 2011 at 11:48 AM, Owen O'Malley <omal...@apache.org> > wrote: > > > On Feb 11, 2011, at 8:02 AM, Eric Sammer wrote: > > > > - allow mrunit to have its own release cycle. This is, I think, the most > >> > > > > important. > >> > > > > If you submit your work to Apache we can evaluate it for inclusion in the > > 0.20.100 branch to get your changes released in a timely manner. > > > I'm thinking in general (beyond the next immediate release). Independent of > where mrunit goes, I think it should leave the contrib tree to facilitate > light weight releases (the dependency on Hadoop proper is a public facing > API - a pure client). I think most projects could benefit from this with > the > exception of things that are tightly coupled to Hadoop releases or touch > non-public APIs. > > +1 for a faster release cycle and using git. I have a couple of patches for mrunit, and it would be nice to get those in separately from hadoop releases. > > > I would actually prefer to move it to Extras or Incubator and leave this > >> within the ASF. > >> > > > > Extras is **NOT** inside of the ASF. Extras is a source hosting system > for > > non-Apache projects that are related to Apache projects. > > > Got it. Thanks for correcting me. I only mentioned it because someone > suggested it to me initially. > > > > Right now, I picked github because of the ability to easily > > collaborate with others (and to use git). > > > > I agree that it is unfortunate that Apache doesn't yet support read-write > > git access. However, you'll find that building a community is easier at > > Apache than at github. > > > > > -- Owen > > > > > > -- > Eric Sammer > twitter: esammer > data: www.cloudera.com >
