Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 18ED810FD2 for ; Wed, 26 Aug 2015 17:20:59 +0000 (UTC) Received: (qmail 82859 invoked by uid 500); 26 Aug 2015 17:20:53 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 82792 invoked by uid 500); 26 Aug 2015 17:20:53 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 82781 invoked by uid 99); 26 Aug 2015 17:20:53 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Aug 2015 17:20:53 +0000 Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 42B841A012E for ; Wed, 26 Aug 2015 17:20:53 +0000 (UTC) Received: by labns7 with SMTP id ns7so6587997lab.0 for ; Wed, 26 Aug 2015 10:20:51 -0700 (PDT) X-Received: by 10.112.53.66 with SMTP id z2mr31525361lbo.121.1440609651870; Wed, 26 Aug 2015 10:20:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.28.138 with HTTP; Wed, 26 Aug 2015 10:20:12 -0700 (PDT) In-Reply-To: References: From: Andrew Purtell Date: Wed, 26 Aug 2015 10:20:12 -0700 Message-ID: Subject: Re: Which version of branch-1 to pick up for product environment To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a11c3bb328f5240051e3a128b --001a11c3bb328f5240051e3a128b Content-Type: text/plain; charset=UTF-8 +1, please try out our latest release line whenever thinking about moving up. This is currently 1.1.x. Over time we will be end-of-lifing old release lines as we introduce newer minor and major releases, and will most likely be doing so from oldest first. On Tue, Aug 25, 2015 at 9:54 AM, Nick Dimiduk wrote: > Unless you've observed some serious issue preventing you from doing so, I > would suggest adopting the newest release available. If you're a > particularly conservative lot, perhaps choose one previous. The 0.98 and > branch-1 releases are all rolling-upgradable between them, so upgrading > production should be relatively painless. For my part at 1.1 RM, I plan to > continue with regular patch releases as long as bug fixes are back-ported, > or until 1.2 is released and matured. That said, we're pushing out nice new > features with each minor release and the only way to get them is to > upgrade. > > On Mon, Aug 24, 2015 at 2:41 AM, Yu Li wrote: > > > Hi All, > > > > As titled, now we're using 0.98.12 in our product env but would like to > do > > some planing for upgrading to branch-1. I could see 1.1.2 is coming soon > > but 1.2 is also in progress w/ some important improvements, so my > question > > basically includes two parts: a) If for planning (not action), which one > is > > better for investigation? 1.1.2 or 1.2? and b) Is there a due date for > 1.2? > > > > Also, I've heard that some famous company is planning to upgrade their > > product cluster to 1.2, and it would be great if anyone could confirm > this > > or share more information. :-P > > > > Any suggestions/information would be highly appreciated, and thanks in > > advance! > > > > > > Best Regards, > > Yu > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) --001a11c3bb328f5240051e3a128b--