Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of jesse.k.yates@gmail.com
 designates 209.85.210.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAB5sDN+fGkt+BggCE+BDkDAwmJtoNumXzdaPU85cZoZ-w0x0zQ@mail.gmail.com>
References: 
 <CAB5sDNKe4A6b3mx-e6dLvbMhMtv_46keFYpN6CY_Z4cpvc2Awg@mail.gmail.com>
 <CALte62zra8i9+pXUjCAJnsHqvXoy70FUbB-T0xZT-AUo_LtJng@mail.gmail.com>
 <CADcMMgFZLDe6Q=3-R+8jzaW4dyFT7j1u0mh2jLcnWFkX-_VgTw@mail.gmail.com>
 <CAOKsKJV=WarqS-4E2uNRbpG_ftW+kzCoA5TqNFm5=R90QCL2SA@mail.gmail.com>
 <CADcMMgE+GdtOa2u8A2kCzrqNNheTYt+cAkO7ZSvE9P904PF+pw@mail.gmail.com>
 <CA+RK=_Cwbq=mEx3-M287=hW82sQ4PhUEQ9v+LckpEVOZhZkvig@mail.gmail.com>
 <CAB5sDNK=M2LWfwLkmSrVkWi7zEQOjeDPCCNROmHmu3Ro-qOA7w@mail.gmail.com>
 <CAOKsKJWbmgG0tR1_K=_1y-eFbvi3TKOhbgH_3ahyOsvX2AkkLQ@mail.gmail.com>
 <CAKYwJ9wc50Efqq42YFUvwvN4f5DiDoeXf6p_Fir7cBwx09zNdg@mail.gmail.com>
 <CAB5sDNKywob4KefmiKmjxADOnEOPPJ8N_TpOvGeOVm=Gmfb7xg@mail.gmail.com>
 <CAB5sDN+fGkt+BggCE+BDkDAwmJtoNumXzdaPU85cZoZ-w0x0zQ@mail.gmail.com>
From: Jesse Yates <jesse.k.yates@gmail.com>
Date: Thu, 24 May 2012 12:29:27 -0700
Message-ID: 
 <CAB5sDN+0Y8Qu897jYRs0BSgv1Ow7cCPaLYX+7aVhb=7eC5=pzQ@mail.gmail.com>
Subject: Re: modularizing trunk
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b3395a7544d0604c0cd462f

--047d7b3395a7544d0604c0cd462f
Content-Type: text/plain; charset=ISO-8859-1

All,

Its taking a little longer than hoped. Thanks for being patient with
commits. Hopefully done shortly - will let you know when we have made the
switch.

-------------------
Jesse Yates
@jesse_yates
jyates.github.com


On Wed, May 23, 2012 at 11:27 PM, Jesse Yates <jesse.k.yates@gmail.com>wrote:

> Hopefully, all the committers are tuckered out from hbasecon and the
> hackathon this week (great events - thanks to everyone who organized and
> made it out) as I'd like to ask to for a virtual lock on the repo until *Noon
> PST Tomorrow (5/24)* so Stack and I can get the modularization committed.
> That means, please no commits until then noon.
>
> After we do the commit, any outstanding patches will need to be rebased
> onto the new trunk (see earlier emails in this thread for more details on
> how this works).
>
> Thanks for your help in this effort.
>
> thanks,
> Jesse
>
> ps. look forward to our third module soon after the switch - hbase-common!
>
> -------------------
> Jesse Yates
> @jesse_yates
> jyates.github.com
>
>
> On Wed, May 9, 2012 at 3:22 PM, Jesse Yates <jesse.k.yates@gmail.com>wrote:
>
>> Created
>> * HBASE-5976 to discuss the name of the initial package
>> * HBASE-5977 to discuss future naming/usage of packages
>>
>> Go nuts.
>>
>>
>> -------------------
>> Jesse Yates
>> @jesse_yates
>> jyates.github.com
>>
>>
>> On Wed, May 9, 2012 at 2:18 PM, Elliott Clark <eclark@stumbleupon.com>wrote:
>>
>>> Starting with hbase-core seems to make sense. If we started with
>>> hbase-server there would be a while until all of the client and other
>>> packages were split up where org.apache.hadoop.hbase.client was in the
>>> hadoop-server jar.
>>>
>>> On Wed, May 9, 2012 at 1:34 PM, Matt Corgan <mcorgan@hotpads.com> wrote:
>>>
>>> > Sorry about that - my intention was not to decide all future module
>>> names,
>>> > just to avoid having both core and common and to illustrate how we were
>>> > heading that direction.
>>> >
>>> >
>>> > On Wed, May 9, 2012 at 1:27 PM, Jesse Yates <jesse.k.yates@gmail.com>
>>> > wrote:
>>> >
>>> > > I was worried this discussion around naming might happen. Should I
>>> open a
>>> > > sub-jira on 4336 for how to name the modules, what future modules
>>> should
>>> > > be, etc.?
>>> > >
>>> > > -Jesse
>>> > > -------------------
>>> > > Jesse Yates
>>> > > @jesse_yates
>>> > > jyates.github.com
>>> > >
>>> > >
>>> > > On Wed, May 9, 2012 at 12:06 PM, Andrew Purtell <apurtell@apache.org
>>> >
>>> > > wrote:
>>> > >
>>> > > > On Wed, May 9, 2012 at 12:01 PM, Stack <stack@duboce.net> wrote:
>>> > > > > On Wed, May 9, 2012 at 11:18 AM, Matt Corgan <
>>> mcorgan@hotpads.com>
>>> > > > wrote:
>>> > > > >> I'd suggest calling this first module hbase-server since the
>>> > majority
>>> > > of
>>> > > > >> the classes are related to the master and regionservers.  Then
>>> we
>>> > can
>>> > > > pull
>>> > > > >> out the fundamental classes (KeyValue, Bytes, etc) into a small
>>> > module
>>> > > > >> called hbase-core.  After that, we can create an hbase-client
>>> module
>>> > > > that
>>> > > > >> only depends on hbase-core (so few or no dependencies).  My main
>>> > point
>>> > > > >> being that we'll want to reserve the name hbase-core for the
>>> actual
>>> > > core
>>> > > > >> classes and not throw everything in there.
>>> > > > >>
>>> > > > >
>>> > > > > We don't want hbase-common and then hbase-core for sure.
>>> > > > >
>>> > > > > The first module rightly should be called hbase-bucket since its
>>> just
>>> > > > > a holding module while we do our sort-through.  Can we figure a
>>> name
>>> > > > > that better conveys the module as so?  hbase-hbase?
>>>  hbase-bucket?
>>> > > > > hbase-99%? hbase-pick-u-part?   hbase-residuum?
>>> > > >
>>> > > > hbase-server is as reasonable as any, right?
>>> > > >
>>> > > > Best regards,
>>> > > >
>>> > > >    - Andy
>>> > > >
>>> > > > Problems worthy of attack prove their worth by hitting back. - Piet
>>> > > > Hein (via Tom White)
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>

--047d7b3395a7544d0604c0cd462f--