Should it be the case that HBASE-751 and/or HBASE-778 are not resolved before August 1, we *will* cut a new release candidate for 0.2.0 and ask for a vote on should this be released with the known bugs (in which case the bugs will be changed to fixing 0.2.1 and 0.3.0).
If the vote is -1, meaning we cannot release 0.2.0 without these fixes, then it will be up to the community (read *you*) to contribute patches that fix these bugs. In this case, we will cut a new release candidate as soon as patches are available, reviewed and have gotten +1 votes from the people who reported them. We want a hbase release that plays with hadoop-0.17 as much as anyone. If 0.2.0 is voted down, we could build a 0.1.x release which is compatible with hadoop-0.17, however this is *not* what we would like to do. --- Jim Kellerman, Senior Engineer; Powerset > -----Original Message----- > From: Rick Hangartner [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 31, 2008 1:21 PM > To: [email protected] > Cc: Chad Walters > Subject: Re: IMPORTANT NOTICE RE: HBase, Stack and Jim Kellerman > > Not to be too reactive here, but in the category of "better > safe than sorry". > > If we are working with HBase 0.2.0 on Hadoop 0.17.1 right > now, and in the unlikely event there is not a HBase 0.2.0 > release (and since the clock is ticking right now to Aug. 1), > is there or will there be any provisions for backwards data > migration from HBase 0.2.0 to HBase > 0.1.3 if the unthinkable happens? > > Previously it was commented here that HBase 0.1.3 can now run > on Hadoop 0.16.x for x > some mininum minor rev. So it > appears the only issue would be backward migration from HBase > 0.2.0 to HBase 0.1.3. > > Thanks, > Rick > > On Jul 30, 2008, at 11:26 PM, Jim Kellerman wrote: > > > My understanding of the situation is as follows: > > > > - We can build releases. > > - We can commit contributions from anyone but ourselves > > - We cannot contribute patches which we develop to resolve > outstanding > > issues > > > > We are trying to nail down the two outstanding issues that are > > blocking 0.2.0. If we can do so before Aug 1, we can commit them. > > > > We will still be available on the mailing lists and the IRC > channel to > > help people with problems or guide them should they choose > to pick up > > an issue that is blocking 0.2.0. > > > > --- > > Jim Kellerman, Senior Engineer; Powerset > > > > > >> -----Original Message----- > >> From: Rick Hangartner [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, July 30, 2008 10:51 PM > >> To: [email protected] > >> Subject: Re: IMPORTANT NOTICE RE: HBase, Stack and Jim Kellerman > >> > >> Can you tell us anything about what this means concerning > an official > >> HBase 0.2.0 release? > >> > >> Regardless of what happens, thanks for everything you and Michael > >> have done bringing HBase to the community. > >> > >> Rick > >> > >> On Jul 30, 2008, at 6:14 PM, Jim Kellerman wrote: > >> > >>> As of Friday August 1, when the acquisition of Powerset by > >> Microsoft > >>> closes, Michael Stack and I will not be able to make further > >>> contributions to HBase until a process is developed within > >> Microsoft > >>> for us to do so. > >>> > >>> We do expect such a process to be developed at this point, since > >>> Microsoft is now a platinum sponsor of Apache.org. However, when > >>> lawyers get involved, who knows how long it will take or > if it will > >>> really happen. Things are looking positive at this point, > >> but now you > >>> know as much as I do. > >>> > >>> Stack and I will be able to commit patches contributed by other > >>> members of the HBase community, so if there was ever an > >> incentive for > >>> others to contribute, this is it! > >>> > >>> We will continue to monitor the mailing lists and the IRC > >> channel, but > >>> beyond that, reviewing patches and committing contributions from > >>> others, our hands are tied. > >>> > >>> Once the situation is resolved (one way or the other) we > >> will will let > >>> the community know. > >>> > >>> --- > >>> Jim Kellerman, Senior Engineer; Powerset > >> > >> > >> No virus found in this incoming message. > >> Checked by AVG - http://www.avg.com > >> Version: 8.0.138 / Virus Database: 270.5.8/1582 - Release > >> Date: 7/30/2008 6:37 PM > >> > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.138 / Virus Database: 270.5.8/1582 - Release > Date: 7/30/2008 6:37 PM >
