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 6733AE306 for ; Thu, 10 Jan 2013 23:14:23 +0000 (UTC) Received: (qmail 54216 invoked by uid 500); 10 Jan 2013 23:14:22 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 54133 invoked by uid 500); 10 Jan 2013 23:14:22 -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 54124 invoked by uid 99); 10 Jan 2013 23:14:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2013 23:14:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of todd@cloudera.com designates 209.85.217.172 as permitted sender) Received: from [209.85.217.172] (HELO mail-lb0-f172.google.com) (209.85.217.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2013 23:14:16 +0000 Received: by mail-lb0-f172.google.com with SMTP id y2so897028lbk.3 for ; Thu, 10 Jan 2013 15:13:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=XhPg1uXNFnvRvMxFteRG/WptO9wNUpD3+lQXTZTxkZA=; b=RRJATW7DLbdU1x6L2dxY+0eBWINIRTIDjuwo7FqCM+3e3VZfLa4Ysd0du5MH35ay+Q JTER1rJi3Pzn/K73WxN3Rvdih3+O4sJwCgAzvnBKlj2KHjJWqXqRCh14TLdBzwfzw7Rr mZUVyKkPiTc+ifXmht4tqZ/5T1Wb4mGkvE6/Kojr1g76169ba38Loo9yqeVlZkQBNbTT mANAnMj+KmzGBj4rRHnRx5WzXw7cKA1flNoNaQDkp7eflIeLAGVUgrMSHbIykLwRLnWb 3McrM2etkKi043M6rdHD/WFnlyWX5ZVf02MRis8yNoc6vVeN+TsDnzEIb9GFZ8YGsDei 3qng== Received: by 10.152.125.237 with SMTP id mt13mr70974669lab.45.1357859636015; Thu, 10 Jan 2013 15:13:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.30.134 with HTTP; Thu, 10 Jan 2013 15:13:35 -0800 (PST) In-Reply-To: References: From: Todd Lipcon Date: Thu, 10 Jan 2013 15:13:35 -0800 Message-ID: Subject: Re: [DISCUSSION] Sorting out issues for 0.96 for (eventual) release To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnpXqYLPPgMtj+uN4kTu7NYQ+uNACN0aOpGIVGxMJeLjvc377C9BQcELiW+X7xM/4fOUKtC X-Virus-Checked: Checked by ClamAV on apache.org I wrote up some stuff on this back in the 0.89 timeframe here: http://wiki.apache.org/hadoop/Hbase/HBaseVersions Could probably do with a refresh of the text, but should mostly still apply. -Todd On Thu, Jan 10, 2013 at 3:11 PM, Andrew Purtell wrote: > I propose to avoid -dev or -beta, and stick with the even/odd scheme we > used for 0.89. We also appended a date stamp instead of minor version, e.g. > 0.89.20100726. Documenting how this departure from our usual numbering > signifies a "developer preview", or whatever we'd like to call it, sounds > like a good idea. > > On Thu, Jan 10, 2013 at 2:55 PM, Jonathan Hsieh wrote: > >> I think that branching scheme makes sense. >> >> We should probably define the intent of even/odd versioning and compat >> rules on the webpage (the how to release instructions and on the >> download links) if we are going to do it so we don't have to explain >> it over and over. If we do this ahead of time, everyone should have >> the same expectations knows what this means. >> >> Also, we could consider probably playing some games with adding -dev >> or -beta after an odd version number. I say this with some >> trepidation - over in Hadoop-land they there are some contentious >> discussions about version numbering and naming that I'd personally >> like to avoid. >> >> Jon. >> >> On Thu, Jan 10, 2013 at 2:15 PM, Andrew Purtell >> wrote: >> > On Thu, Jan 10, 2013 at 2:00 PM, Stack wrote: >> > >> >> How do we want to run it? Branch 0.96 and then 0.95s are branched from >> >> 0.96? (As in the past, 0.95.0, 0.95.1, etc., would come with no >> guarantees >> >> other than it basically works and it is allowed that 0.95.1 may not be >> >> compatible with 0.95.0, etc.). >> >> >> > >> > >> > +1 >> > >> > -- >> > Best regards, >> > >> > - Andy >> > >> > Problems worthy of attack prove their worth by hitting back. - Piet Hein >> > (via Tom White) >> >> >> >> -- >> // 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) -- Todd Lipcon Software Engineer, Cloudera