I agree with Ryan, and what we actually need would be a Known Issues document shipped with all releases. For 0.20, lack of sync should be the top item.
J-D On Wed, Jun 9, 2010 at 1:07 PM, Ryan Rawson <[email protected]> wrote: > Every release we ship has bugs, some known, most unknown. I have > previously argued against perfectionism in our releases (perfect is > the enemy of good), since if a bug isn't so bad and is in a previous > release, then maybe we shouldn't hold up a release which has lots of > other important fixes. The focus is on keeping forward momentum and > preventing regressions. I think people might generally appreciate > more but smaller releases with fewer fixes (eg: 0.20.5 has about 18 > fixes which seems pretty good, not too high not too low). > > > > > On Wed, Jun 9, 2010 at 11:21 AM, Andrew Purtell <[email protected]> wrote: >> This is a slippery slope. >> >> --- On Tue, 6/8/10, Todd Lipcon <[email protected]> wrote: >> >>> From: Todd Lipcon <[email protected]> >>> Subject: Re: [VOTE] Shall we release hbase-0.20.5 Release Candidate 2 as >>> hbase-0.20.5? >>> To: [email protected] >>> Date: Tuesday, June 8, 2010, 7:26 PM >>> On Tue, Jun 8, 2010 at 6:11 PM, Ryan >>> Rawson <[email protected]> >>> wrote: >>> >>> > Should we ship 0.20.5 with the fixes as is? The >>> bug is very rare, and >>> > while some people might come across it, it is in >>> 0.20.4 which is known >>> > to be bad. >>> > >>> > We need to get a better 0.20 out there than >>> 0.20.4. What we have is >>> > pretty good, and we can fix the next issue in 0.20.6. >>> > >>> > >>> Actually that sounds fair to me. Ignore my -1 conditional >>> on us doing an >>> 0.20.6 sometime in the next couple weeks. >>> >>> I'll try to do some cluster testing this week to actually >>> put a +1 in >>> instead of just retracting a -1 :) >>> >>> -Todd >>> >>> >>> > -ryan >>> > >>> > On Tue, Jun 8, 2010 at 5:42 PM, Todd Lipcon <[email protected]> >>> wrote: >>> > > Unfortunately -1: >>> > > https://issues.apache.org/jira/browse/HBASE-2670affects >>> > > branch as well. >>> > > >>> > > I'm working on a fix, will target both branch and >>> trunk, but may be a >>> > couple >>> > > days before we can thoroughly test it (this bug >>> is devious) >>> > > >>> > > -Todd >>> > > >>> > > On Mon, Jun 7, 2010 at 1:09 PM, Stack <[email protected]> >>> wrote: >>> > > >>> > >> I've posted an hbase 0.20.5 release candidate >>> 2 here: >>> > >> >>> > >> http://people.apache.org/~stack/hbase-0.20.5-candidate-2/ >>> > >> >>> > >> Should we release this candidate as hbase >>> 0.20.5? >>> > >> >>> > >> It has 18 fixes: http://su.pr/1prW9y >>> > >> >>> > >> Please take it for a test spin if you have a >>> chance. Vote closes >>> > >> Friday, the 11th of June. >>> > >> >>> > >> Yours, >>> > >> Your HBase Homies >>> > >> >>> > > >>> > > >>> > > >>> > > -- >>> > > Todd Lipcon >>> > > Software Engineer, Cloudera >>> > > >>> > >>> >>> >>> >>> -- >>> Todd Lipcon >>> Software Engineer, Cloudera >>> >> >> >> >> >> >
