When this first went in we were making an incompatible branch release already. I think the current situation is pretty close.
However, IMO let's just do this on trunk. The current very simple approach works for some straightforward cases but I have a dev group reporting some odd behavior that I need to dig into next week. Doing this right may be more complicated. - Andy --- On Sat, 6/19/10, Dave Latham <lat...@davelink.net> wrote: > From: Dave Latham <lat...@davelink.net> > Subject: Re: [VOTE] Shall we release hbase-0.20.5 Release Candidate 4 as > hbase-0.20.5? > To: dev@hbase.apache.org > Date: Saturday, June 19, 2010, 8:59 AM > The inclusion of HBASE-1537 changes > the Scan serialization format, making > clients incompatible with previous 0.20.x releases. > Is that ok? > > Dave > > On Sat, Jun 19, 2010 at 12:33 AM, Stack <st...@duboce.net> > wrote: > > > I've posted an hbase 0.20.5 release candidate 4 here: > > > > > >http://people.apache.org/~stack/hbase-0.20.5-candidate-4/<http://people.apache.org/%7Estack/hbase-0.20.5-candidate-4/> > > > > There have been 24 issues addressed since the release > of hbase-0.20.4 [1]. > > > > Should we release this candidate as hbase 0.20.5? > > > > Please take it for a test spin if you have a > chance. Vote closes > > Wednesday, June 23rd. > > > > Thanks, > > Your HBase Team > > > > 1. http://su.pr/1prW9y > > >
