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 CC058104E3 for ; Thu, 2 Jan 2014 21:20:48 +0000 (UTC) Received: (qmail 48734 invoked by uid 500); 2 Jan 2014 21:20:48 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 48678 invoked by uid 500); 2 Jan 2014 21:20:48 -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 48666 invoked by uid 99); 2 Jan 2014 21:20:48 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jan 2014 21:20:47 +0000 Received: from localhost (HELO mail-wg0-f46.google.com) (127.0.0.1) (smtp-auth username enis, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jan 2014 21:20:47 +0000 Received: by mail-wg0-f46.google.com with SMTP id m15so12701902wgh.25 for ; Thu, 02 Jan 2014 13:20:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Lgx3H+1FkhyTfAYYrsPDs6fCm9sQaW8nMB+KCzC/KhI=; b=XkLjbIqoB/xI8K0sgYcKuBJ4MZ0/2we9e7gj+GzZbzidlDnHWfmZ8x8laRdmvYghyw zJl+wjm9aBLXfxPKnHHOSwjuKtTJwoygAwKj2UU9AL/dDbmyMPAaHYy68xY0cp9AdSf2 V/9Z/pV+YS+CleQqvxNeISdO4u+Ug0IhAVV6/MZd2TVQEQ6w+aMhoUL0j15iNvebLXvc 9PAtImm2GLJMLL3RH/WkeSFY+zDn2WOwyI7FmWQwMSZ7TMLF4IyjHe8YmGkEBzumdJIA 3z+ebRvkJIrn/W24LAF781FzMgeiS9jy7oWSBPS/HBro09qeuBvylFLS61aj3lXiNyg8 poCw== X-Received: by 10.180.21.101 with SMTP id u5mr18543647wie.38.1388697646034; Thu, 02 Jan 2014 13:20:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.48.15 with HTTP; Thu, 2 Jan 2014 13:20:25 -0800 (PST) In-Reply-To: References: <1388692333.46462.YahooMailNeo@web140606.mail.bf1.yahoo.com> From: =?UTF-8?Q?Enis_S=C3=B6ztutar?= Date: Thu, 2 Jan 2014 13:20:25 -0800 Message-ID: Subject: Re: DISCUSSION: 1.0.0 To: "dev@hbase.apache.org" Cc: lars hofhansl Content-Type: multipart/alternative; boundary=047d7bb70ca2e4758b04ef035d55 --047d7bb70ca2e4758b04ef035d55 Content-Type: text/plain; charset=UTF-8 I think whether we will need a new RM will depend on the decision to release 1.0 from 0.98 branches or 0.99 branches(current trunk). We can do the previous practice of releasing 0.99.0, then turning 0.99.x as the 1.0.0. In that case, I can also volunteer as well. Enis On Thu, Jan 2, 2014 at 12:53 PM, Andrew Purtell wrote: > Yeah, I want to have an 0.98 RC in the test rig by week's end. So that > would be artifacts for voting available next week. > > My suggestion is a 1.0 release 3 months or so from when 0.98.0 ships. This > is arbitrary, but seems reasonable to me as enough time to get some > production experience with 0.96 and/or 0.98, sort out the remaining API > issues for a 1.0 caliber release, and do whatever else needs doing > (tooling). > > Having one RM for any given release will avoid split-brain issues. :-) > > > On Thu, Jan 2, 2014 at 11:52 AM, lars hofhansl wrote: > > > I'd be volunteering for RM.Maybe do it together? > > Personally I'd like to see some heavy production usage of 0.96 or 0.98 in > > the community before can call the new "DNA" (HBase >= 0.96) 1.0. > > > > -- Lars > > > > > > > > ________________________________ > > From: Stack > > To: HBase Dev List > > Sent: Thursday, January 2, 2014 11:26 AM > > Subject: DISCUSSION: 1.0.0 > > > > > > Andrew is talking of the first 0.98RC being imminent. > > > > Time to start in on the release that will follow 0.98.x. We seem to all > be > > good with calling it 1.0.0. Speak up if you think different. (I just > added > > a 1.0.0 version to JIRA). > > > > + What should 1.0.0 have in it beyond what is in 0.98. > > + Why can't 1.0.0 just be 0.98.0, or 0.98.1 altogether? > > + When should it come out? I'm thinking soon after 0.98. Feb/March? > > (Presuming 0.98 ships in Jan). > > + Who should RM it? (I could but perhaps others are interested). > > > > What else should we consider achieving the state of 1.0.0ness? > > > > Happy New Year all, > > St.Ack > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) > --047d7bb70ca2e4758b04ef035d55--