hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Kimball <aa...@cloudera.com>
Subject Re: Release plans
Date Fri, 19 Feb 2010 21:48:00 GMT
+1 from me.

I agree with Stack; faster release cycles will help keep the project focused
and get code testing and soaking in more environments.

- Aaron

On Fri, Feb 19, 2010 at 1:44 PM, Eli Collins <eli@cloudera.com> wrote:

> On Thu, Feb 18, 2010 at 8:36 PM, Stack <stack@duboce.net> wrote:
> > On Thu, Feb 18, 2010 at 5:02 PM, Owen O'Malley <omalley@apache.org>
> wrote:
> >> Yahoo doesn't care. Even if we rebase the 0.21 branch, because of the
> >> timing, Yahoo will probably never deploy it. (It take months to push a
> >> release through QA and production testing, as I wrote the security
> release
> >> will hit the pipeline this year (code complete in february, first
> >> integration cluster in april, on all production clusters by august).
> Yahoo
> >> can't handle another big release until january 2011.
> >
> > I haven't done a survey but my guess is that the HBase crew would
> > favor putting out the current 0.21 branch as 0.21 rather than
> > rebasing.  To us, hdfs and its flush, in testing, runs great.  I'm
> > with Konstantin and Sanjay that a release is pretty close and that a
> > rebasing pulling in new features means more months even allowing for
> > the Todd stabilizing constant.
>
> Given that Yahoo and others plan to skip 21, and the HBase crowd could
> actually use 21 and have invested in the current branch's contents, it
> sounds like we should try to get the current branch released. Anyone
> object?
>
> Thanks,
> Eli
>

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