HBASE-2473 is a new feature.  0.21 is equivalent to 0.89 and 0.90 (trunk).  
0.89 are dev releases off trunk which will be release as 0.90.

0.20 branch is an old branch that will not have new features added to it, just 
bug fixes.  All new features should be done against trunk only.

http://hbaseblog.com/2010/07/04/hug11-hbase-0-90-preview-wrap-up/

There's more info about the versions in the deck on that blog post.

JG

> -----Original Message-----
> From: Ted Yu [mailto:yuzhih...@gmail.com]
> Sent: Sunday, July 25, 2010 7:30 AM
> To: dev@hbase.apache.org
> Subject: Re: [VOTE] Shall we release hbase-0.20.6 Release Candidate 1
> as hbase-0.20.6?
> 
> Since HBASE-2473 is marked fixed for 0.21, some advice regarding the
> roadmap
> for 0.21 vs. 0.20.6 vs 0.89 would help us decide which version to use.
> 
> Thanks
> 
> On Sat, Jul 24, 2010 at 10:08 PM, Ted Yu <yuzhih...@gmail.com> wrote:
> 
> > I don't see HBASE-2473 among the 8 fixes of 0.20.6
> > I checked 0.20.5 source code and didn't seem to find the patch there
> > either.
> >
> > Please advise.
> >
> >
> > On Wed, Jul 21, 2010 at 9:09 AM, Dave Latham <lat...@davelink.net>
> wrote:
> >
> >> For what it's worth, I've been running the 0.20 branch at r963948,
> which
> >> is
> >> the same as this release candidate except for
> >> https://issues.apache.org/jira/browse/HBASE-2837.  Haven't had any
> >> problems.
> >>
> >> Dave
> >>
> >> On Mon, Jul 19, 2010 at 9:15 PM, Stack <st...@duboce.net> wrote:
> >>
> >> > I've posted an hbase 0.20.6 release candidate 5 here:
> >> >
> >> >  http://people.apache.org/~stack/hbase-0.20.6-candidate-
> 1/<http://people.apache.org/%7Estack/hbase-0.20.6-candidate-1/>
> >> <http://people.apache.org/%7Estack/hbase-0.20.6-candidate-1/>
> >> >
> >> > There have been 8 fixes since the release of hbase-0.20.5 [1].
> >> >
> >> > Should we release this candidate as hbase 0.20.6?
> >> >
> >> > Please take it for a test spin if you have a chance.  Vote closes
> >> > Monday July 26th.
> >> >
> >> > Thanks,
> >> > Your HBase Team
> >> >
> >> > 1. http://su.pr/1kRdZN
> >> >
> >>
> >
> >

Reply via email to