Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 59910 invoked from network); 9 Apr 2010 06:10:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 Apr 2010 06:10:22 -0000 Received: (qmail 28137 invoked by uid 500); 9 Apr 2010 06:10:21 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 28032 invoked by uid 500); 9 Apr 2010 06:10:21 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 28024 invoked by uid 99); 9 Apr 2010 06:10:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Apr 2010 06:10:21 +0000 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jaybooth@gmail.com designates 209.85.160.176 as permitted sender) Received: from [209.85.160.176] (HELO mail-gy0-f176.google.com) (209.85.160.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Apr 2010 06:10:16 +0000 Received: by gyf1 with SMTP id 1so1549675gyf.35 for ; Thu, 08 Apr 2010 23:09:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=DicNeCDD552o3UUGdrTWUeQXdnBJSck/KI0f/J2v7Vs=; b=vTDpa1G3jUqM3nZ5BjTTzQOR0uYPsvijPkltG/j6shyczS1j3KcinvmR4/9W6X7iSy Gf4WNHXbtk1h5/3l7d/Ec+O2R1gDPJfB7oTCgHAoIXR5+tFE9e8oBmfUvH/KUqleRZbw VGs4ljKNDNgBA9E+nJ+ZC/MO0sVDoqM/CAano= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=J93Ze785EUMOO0jl2iz7ytNDM5yhJgyCFsTXPbANmks3XlxkTcTwmQq1a4q7D+kFxW S1Y3Jc5uVWiZ4nSIYNEJIFH8B1v9EFYSyEUfrKe0p2ARcxAAYjCw6tHVf6qTnrsUsCgN izyPTgZiqVRW61x7bQiGsqNV4x2OwywbpF+QE= MIME-Version: 1.0 Received: by 10.100.201.9 with HTTP; Thu, 8 Apr 2010 23:09:54 -0700 (PDT) In-Reply-To: References: <3F1902B5-BAD3-440D-8D35-6EBC3297B939@yahoo-inc.com> Date: Fri, 9 Apr 2010 02:09:54 -0400 Received: by 10.101.136.33 with SMTP id o33mr1894029ann.63.1270793394269; Thu, 08 Apr 2010 23:09:54 -0700 (PDT) Message-ID: Subject: Re: [DISCUSS] HBase as TLP From: Jay Booth To: general@hadoop.apache.org Content-Type: multipart/alternative; boundary=001636d3496ad942aa0483c7a442 --001636d3496ad942aa0483c7a442 Content-Type: text/plain; charset=ISO-8859-1 Alright, I totally agree. Thanks for putting it that way. -Jay On Fri, Apr 9, 2010 at 12:07 AM, Imran M Yousuf wrote: > +1 > > I feel the same. From following HBase seeing its releases depending > directly on Hadoop release gets me thinking... > > Best regards, > > Imran > > On Fri, Apr 9, 2010 at 9:45 AM, Tom White wrote: > > Eclipse does big bang releases of multiple components, but I believe > > it requires a huge amount of coordination and planning. Instead, I > > think the direction Hadoop should move in is to stabilize and clearly > > demarcate its core filesystem and MapReduce interfaces, so that > > projects like HBase, Pig, and Hive can run against multiple versions > > of core. Their release cycles are already largely decoupled from core, > > so the question about whether they become TLPs is more to do with > > project governance than with release coordination. > > > > Cheers, > > Tom > > > > On Thu, Apr 8, 2010 at 8:40 PM, Jay Booth wrote: > >> Not sure exactly what I meant by "1.0 of what", "Hadoop" I guess, I was > >> trying to address the concerns raised, which I share -- Alan's concern > is > >> that if the projects are completely separate from each other, that might > >> decrease visibility as to the demands they're placing on each other when > >> integrated, and St.Ack mentioned the frankenstein factor which I think > we've > >> all felt some pain from, and which may get worse after the project > split. > >> What's the standard way to deploy the three, even? Is there one? > >> > >> If the PMCs jointly maintained some sort of 'stable integrated build' > which > >> took in new releases from the TLPs as they were released after a soak > >> period, it could provide a common touchstone that bugs could be tested > >> against and cross-component patches delivered against, potentially > >> increasing visibility of cross-component issues while providing a less > >> cobbled-together system to administrate. On the other side, though, if > >> executed wrong, you'd be creating a committee of committees and possibly > >> undoing some of the benefits of going TLP in the first place, especially > if > >> politics heat up over what goes into the 'standard' build. I think it > could > >> be viable though. > >> > >> > >> > >> On Thu, Apr 8, 2010 at 10:02 PM, Arun C Murthy > wrote: > >> > >>> > >>> On Apr 8, 2010, at 6:41 PM, Jay Booth wrote: > >>> > >>> What if the projects were: > >>>> > >>>> A) split out to TLPs because they do seem to have reached that level > of > >>>> individual community > >>>> > >>>> but, > >>>> > >>>> B) The projects could somehow jointly put out an integrated build > >>>> containing the above projects and let users run whatever they want out > of > >>>> it? > >>>> > >>>> That would require a lot of coordination but would make a heck of a > 1.0 > >>>> release, > >>>> > >>> > >>> > >>> 1.0 release of what? > >>> > >>> Arun > >>> > >> > > > > > > -- > Imran M Yousuf > Entrepreneur & Software Engineer > Smart IT Engineering > Dhaka, Bangladesh > Email: imran@smartitengineering.com > Blog: http://imyousuf-tech.blogs.smartitengineering.com/ > Mobile: +880-1711402557 > --001636d3496ad942aa0483c7a442--