hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lars George <lars.geo...@gmail.com>
Subject Re: 0.20.3 in sight
Date Mon, 28 Dec 2009 23:04:34 GMT
Hey,

I can fix mine this week. Easy fix.

Lars

On Dec 28, 2009, at 22:35, Jean-Daniel Cryans <jdcryans@apache.org>  
wrote:

> I added a comment in 1636 saying that I will close it upon release...
> some fixes were kinda exotic and I'm worried about stability. I'll do
> some more testing on branch.
>
> I will take care of HBASE-2025 and see where the problem is.
>
> Not sure what to do with 2042...
>
> Thx Andy!
>
> J-D
>
> On Mon, Dec 28, 2009 at 1:31 PM, Andrew Purtell  
> <apurtell@apache.org> wrote:
>> There are 10 open issues: http://su.pr/1w5LBO
>>
>> I can finish up HBASE-1937 this week.
>>
>> Stack wants HBASE-2037 in.
>>
>> HBASE-2042 is marked as a blocker.
>>
>> I think we also do not want a repeat of HBASE-2025, so I raised it  
>> to blocker.
>>
>> Does HBASE-2064/5 resolve HBASE-1636?
>>
>>   - Andy
>>
>>
>>
>> ----- Original Message ----
>>> From: Jean-Daniel Cryans <jdcryans@apache.org>
>>> To: HBase Dev List <hbase-dev@hadoop.apache.org>
>>> Sent: Mon, December 28, 2009 10:14:00 AM
>>> Subject: 0.20.3 in sight
>>>
>>> Hi devs,
>>>
>>> HBASE-2064/5 are big enough cases to justify a new minor release but
>>> we also have other much needed fixes like higher default tick time,
>>> fix to empty oldlogfile and goodies like a wiser detection of node's
>>> address for HQuorumPeer, EC2 stuff, zktop and much more. So, please
>>> review your cases and fix/punt/etc.
>>>
>>> We also have to decide what's happening to HBASE-1935. IIRC we  
>>> said it
>>> was ok but it's still not committed.
>>>
>>> It would be nice to release a RC next week.
>>>
>>> Thx!
>>>
>>> J-D
>>
>>
>>
>>
>>
>>

Mime
View raw message