Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E336BE816 for ; Fri, 11 Jan 2013 16:16:39 +0000 (UTC) Received: (qmail 66904 invoked by uid 500); 11 Jan 2013 16:16:39 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 66757 invoked by uid 500); 11 Jan 2013 16:16:39 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 66746 invoked by uid 99); 11 Jan 2013 16:16:39 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 16:16:39 +0000 Received: from localhost (HELO mail-oa0-f50.google.com) (127.0.0.1) (smtp-auth username apurtell, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 16:16:38 +0000 Received: by mail-oa0-f50.google.com with SMTP id n16so1934527oag.37 for ; Fri, 11 Jan 2013 08:16:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.1.73 with SMTP id 9mr44096403oek.130.1357920997910; Fri, 11 Jan 2013 08:16:37 -0800 (PST) Received: by 10.60.54.97 with HTTP; Fri, 11 Jan 2013 08:16:37 -0800 (PST) In-Reply-To: References: <1357843573.19146.YahooMailNeo@web140601.mail.bf1.yahoo.com> <1357875261.14274.YahooMailNeo@web140604.mail.bf1.yahoo.com> <1357882603.14418.YahooMailNeo@web140603.mail.bf1.yahoo.com> Date: Fri, 11 Jan 2013 08:16:37 -0800 Message-ID: Subject: Re: Upcoming merge of snapshots branch into trunk. (HBASE-6055 and HABSE-7290) From: Andrew Purtell To: "dev@hbase.apache.org" Cc: lars hofhansl , Stack Content-Type: multipart/alternative; boundary=e89a8fb20660b6a7aa04d3059e37 --e89a8fb20660b6a7aa04d3059e37 Content-Type: text/plain; charset=ISO-8859-1 Intel will be putting effort into stabilizing 0.96 for production use too. On Friday, January 11, 2013, Jonathan Hsieh wrote: > Cloudera Hat: We are customer driven when it comes to features and > this is oft requested. 0.96 is a compatiblity breaking release and we > have some constraints there. Snapshots is mostly an additive feature > so it is technically possible with minor compatibility concerns. > > Apache Hat: Keeping features to new versions makes the most sense - it > keeps stable versions stable and encourages folks to move to newer > shinier versions. :). Ideally, with a healthy Apache project that > releases regularly, the release schedule and feature set of > distributions shouldn't affect the natural release cadence and feature > set of the apache project. > > At the moment the best guess for when 0.96 gets released is unknown. > There will be a non-trivial amount of time necessary to harden > snapshots as well as all the other additions to that version. Its > pretty plain to see that Cloudera and HWX are putting significant > efforts into readying 0.96 as well. > > Jon. > > On Thu, Jan 10, 2013 at 9:36 PM, lars hofhansl > > wrote: > > Oh, I meant the 1.0.x, 1.1.x, 2.x.x, etc version. Yeah, the -beta is not > a good idea (IMHO). > > > > > > I have to ask the Cloudera and Hortonworks folks then: Why not wait > until 0.96 is stable? Why backport snapshots to 0.94? > > > > -- Lars > > > > > > > > ________________________________ > > From: Stack > > > To: HBase Dev List >; lars hofhansl > > > > Sent: Thursday, January 10, 2013 9:19 PM > > Subject: Re: Upcoming merge of snapshots branch into trunk. (HBASE-6055 > and HABSE-7290) > > > > > > On Thu, Jan 10, 2013 at 7:34 PM, lars hofhansl > > wrote: > > > > Eventually we should switch to semantic versioning (like Hadoop). > >> > >> > > > > The -beta stuff? Nah, at least in Hadoop, it has been arbitrarily > applied (and contended). Lets not use Hadoop as an example. We have some > precedent for linux-y odd is unstable, even is stable. Lets hold to it I'd > say. > > > > > > It also depends on the timing of 0.96. > >>The fact that two companies want to port this to 0.94 seems to indicate > low confidence that we can ship a stable 0.96 soon. > >> > >> > > > > I think it is more that 0.96.0 is a singularity. Including 0.96 in a > downstreamer's bundle only makes sense when the vendor is moving to a new > major version. These major versions happen on a less frequent cycle. We > just need to make sure 0.96 is out and well-baked the next time these > cycles come around. > > > > St.Ack > > > > -- > // Jonathan Hsieh (shay) > // Software Engineer, Cloudera > // jon@cloudera.com > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) --e89a8fb20660b6a7aa04d3059e37--