Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # dev >> HBase releases...

Copy link to this message
Re: HBase releases...
Doing the linux release style works well if we have enough people who are
willing and able to maintain a bunch of separate branches. As it stands the
HBase community is pretty small compared to Linux, and I don't know how many
people would be willing to maintain a release - almost a full time job on
its own, leaving little time for writing code.

Maybe before we do some of the 'early' branches we get someone from the
community to volunteer to maintain it?

I'm also worried that could lead to a LOT of fracturing in releases (hence
the million and a half flavors of linux), which I feel is not all that good
for the community (though maybe good for lining people's
**cough**RedHat**cough** pockets).


>So, I am not big fan of time based releases. What I am thinking to nudge
'>feels right' point a bit sooner. :)

That is kind of what I was getting at. I wanted to formalize the 'feels
right' process, so we don't start doing massive code drops.

>Software engineers (me included) tend to want to cram as many features as
>into a release and sometimes it is good to make this tendency conscious and
>counter this a bit to avoid feature bloat. (not saying that is a problem in
HBase, just a
>general statement here).

I'm all for adding good stuff (and I can be as much a culprit as anyone ;)

>For example, what if we had branched right after coprocessors went in.
>that been useful?

That is definitely fair that we have done some solid stuff since. But CPs
are the exception, not the rule. Hence, the provision that we can vote to
keep going.

Basically, I'm also lobbying for a way to hit a 'feels right' sooner, and I
think metrics (rather than emotion) is the way to go.

-Jesse Yates

On Tue, Oct 11, 2011 at 11:19 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:

> I just wrote in parallel response to Jesse that I am not a big fan of
> time based releases :)
> The way you describe it it makes sense, though.
> o we'd branch at given intervals (once a week/month/quarter/whatever)
> o some releases will turn out to be good ones, users could standardize on
> those
> o we would only provide updates in a form of a new release, or maybe a dev
> and stable release
> Might be hard to get bigger features in that way; although Linux
> manages that with merge windows.
> Seems like this'd be a big shift. Hence my softer approach to just change
> a bit what 'it feels right' means.
> -- Lars
> ----- Original Message -----
> From: Todd Lipcon <[EMAIL PROTECTED]>
> Cc:
> Sent: Tuesday, October 11, 2011 11:02 PM
> Subject: Re: HBase releases...
> I was discussing this with a few other contributors a while back. In
> my mind there are two ways to do it:
> a) feature based releases that we test the crap out of and decide are
> stable. We can't really do this more than once a year, I don't think.
> b) time based releases where we make few guarantees beyond "it appears
> to work". We assume that once a year or so, major users and
> distributors latch on to one of these that feels good, and start
> maintaining it as a stable/maintenance series.
> B is the Linux model. No one in their right mind runs the latest
> kernel.org in production - but certain vintages of kernel gather
> enough folks around them, pick up a stable maintainer, etc, and after
> a while become pretty rock solid. For example, 2.6.18 and 2.6.32 seem
> to be popular kernel vintages.
> I'm personally of the mind that B is the more reasonable model. Keeps
> a release train ticking all the time, allows experimental users to get
> new features fast, and avoids the burden of feeling that any release
> we do has to be perfect. It's also often hard to say what "vintage"
> will be good until it's been out in the wild for a little while - for
> example, the 0.89.20100621 dev release turned out to be pretty decent
> despite being branded as a dev release. The later releases in that
> series had some more major problems.
> The risk with the "B" model is that everyone might end up on different