Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 84281 invoked from network); 23 Apr 2010 07:22:54 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Apr 2010 07:22:54 -0000 Received: (qmail 61282 invoked by uid 500); 23 Apr 2010 07:22:54 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 61137 invoked by uid 500); 23 Apr 2010 07:22:54 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 61129 invoked by uid 99); 23 Apr 2010 07:22:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Apr 2010 07:22:53 +0000 X-ASF-Spam-Status: No, hits=1.1 required=10.0 tests=FREEMAIL_FROM,FRT_ADOBE2,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.221.193 as permitted sender) Received: from [209.85.221.193] (HELO mail-qy0-f193.google.com) (209.85.221.193) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Apr 2010 07:22:47 +0000 Received: by qyk31 with SMTP id 31so12067410qyk.20 for ; Fri, 23 Apr 2010 00:22:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:received:message-id:subject :from:to:content-type:content-transfer-encoding; bh=iG5oa1DZux4wQ4LjA4CLbtGcelh6bep5OiJKPjUoQxc=; b=qGKlFUDKyl2djIwc4Fzk47tOrcabf/MCzrweqt0fRPcR3i9OuKGvFxXfhgm0110kRK Y7sMHrTTzqz3T4/VlcOBOxlshmEefRvhPaSMk2IGLEHh1XEV27Llo3j9wLVSdLIBgdJa En3TNX/NrNt1yVQfkMNPEd0XNNOiyiSUL3Euc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=DJdn259LIVI7ixdyLG6Y4qz30XHy0n3MEz8EPtwFyQJ0xZShab6hKi1rhcnTnxrxPq SNSr5ExpbDMRzjrW5aTru1t91FxCVWnNHf9fXWyL7jegGzgXi8Ww5CztoBJdEuBPb2hs yKJ9ob0xiylMgP/jsVMOXPsExcYpkjtvDc8ZU= MIME-Version: 1.0 Sender: saint.ack@gmail.com Received: by 10.229.18.11 with HTTP; Fri, 23 Apr 2010 00:22:26 -0700 (PDT) In-Reply-To: <8D66B74984F9564BBB25C3C67D630F2D67075597@SC-MBXC1.TheFacebook.com> References: <65E1B68E-008C-4B1E-8157-77D3DEBF2FB1@adobe.com> <8D66B74984F9564BBB25C3C67D630F2D67075597@SC-MBXC1.TheFacebook.com> Date: Fri, 23 Apr 2010 00:22:26 -0700 X-Google-Sender-Auth: 0a4aab98c3229f73 Received: by 10.229.242.74 with SMTP id lh10mr6592916qcb.61.1272007346593; Fri, 23 Apr 2010 00:22:26 -0700 (PDT) Message-ID: Subject: Re: HBase move to Apache Top Level Project From: Stack To: hbase-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Apr 22, 2010 at 11:44 PM, Jonathan Gray wrote: > Now might also be the time to think about breaking from hadoop numbering = (I think this idea has been floating around since the first version we sync= ed). > > We've already agreed to break client compatibility for 0.20.5 and it's mo= re than a minor revision. =A0And I'm sure we'll have another release betwee= n 0.20.5 and 0.21. > So, the new version could be 0.21 but thats not 'breaking from hadoop numbering' and it can't be 1.0.0 .... yet. What should it be? 0.99.0 is kinda dumb. 0.3.0? (We went as far as 0.2.0 on old numbering system). 0.3.0 will be less than 0.21.0 so will mess w/ packaging systems. 0.30.0? > It's also clear that this is going to be by far our most solid release to= date and so might be worthy of new shiny versioning/packaging as a TLP. = =A0Website/docs/wiki refresher to boot. > > Changing the package names is way more invasive to client code but I'm al= ways +1 on making stuff shorter. Might have to keep around the old stuff deprecated. St.Ack > > > Anyways, I'm not doing much production cluster maintenance these days so = these changes would impact me way less than others. =A0Will welcome pushbac= k if you guys don't want to deal with this. > > JG > >> -----Original Message----- >> From: Ryan Rawson [mailto:ryanobjc@gmail.com] >> Sent: Thursday, April 22, 2010 11:20 PM >> To: hbase-dev@hadoop.apache.org >> Subject: Re: HBase move to Apache Top Level Project >> >> I am somewhat interested in this :-) >> >> But it can make life difficult for our users... thoughts people? >> >> On Thu, Apr 22, 2010 at 11:17 PM, Karthik K wrote: >> > This is great news. Congrats HBase team. >> > >> > (Does this mean, the packages would be refactored as o.a.hbase.* in >> the >> > trunk ? ). >> > >> > -- >> > =A0Karthik. >> > >> > >> > On Thu, Apr 22, 2010 at 10:47 PM, Cosmin Lehene >> wrote: >> > >> >> This is great news! >> >> >> >> On Apr 22, 2010, at 8:32 PM, Stack wrote: >> >> >> >> > The board yesterday passed a resolution making HBase a TLP. >> >> > >> >> > I filed an infrastructure issue to start the move: >> >> > >> >> > https://issues.apache.org/jira/browse/INFRA-2641 >> >> > >> >> > The primary disruption to developers will be when the subversion >> >> > repository is renamed. =A0We'll send out a note before we do this, >> then >> >> > developers can use 'svn switch' to update their repos (There is no >> >> > apache git repo that I know of... I asked just in case) >> >> > >> >> We already use the apache git.apache.org mirror for HBase. I've also >> seen >> >> the GitHub mirror http://github.com/apache/hbase and thought there >> might >> >> be some plans for migration. >> >> >> >> > One other issue is the wiki. =A0I don't think it's easy to rename a >> >> > subtree from a Moin Moin wiki to a new wiki. =A0Fortunately we don'= t >> >> > have many wiki pages and could cut and paste them manually. >> >> > Alternately, we could switch to using confluence for our wiki. >> >> > Thoughts? >> >> > >> >> Confluence has a good integration with Jira (being both developed by >> >> Atlassian). It's functionally advanced and looks better. So +1 for >> that as >> >> well. >> >> >> >> Cosmin >> >> >> >> > St.Ack >> >> > (Above shamelessly a copy of Doug's mail to the Avro list) >> >> >> >> >> > >