You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by Ivan Kelly <iv...@apache.org> on 2012/11/23 16:43:29 UTC
[DISCUSS] Preparation for BookKeeper 4.2.0 Release
Hi guys,
Things have been progressing well lately, so I think it's time to
start thinking about getting 4.2.0 release out of the door. The main
features I'd like for this are,
- AutoRecovery: autorerelication for ledgers in the case of bookie
failure
- Metastore: metadata storage, to allow other metadata backends to be
plugged into hedwig & bookkeeper
- Readonly bookie mode
- Revised bookie GC
The last one I'm not 100% sure about, but anything other than these
and bugfixes should wait until 4.3.0.
I'd like to try and get a first release candidate cut next week. Also,
any help with patch reviews would be appreciated. I'm currently
setting up automated testing for patches, which should check all the
basic things automatically.
Regards
Ivan
Re: [DISCUSS] Preparation for BookKeeper 4.2.0 Release
Posted by fangmin lv <lv...@gmail.com>.
Hi Ivan,
>From my point, I think it's fine to put the Revisited bookie GC to 4.3.0
release.
The patch to GC is just submitted and there is not enough time to review
it, so it's better to delay, just schedule the plan as you wish.
Thanks,
Fangmin
On Fri, Nov 23, 2012 at 11:43 PM, Ivan Kelly <iv...@apache.org> wrote:
> Hi guys,
>
> Things have been progressing well lately, so I think it's time to
> start thinking about getting 4.2.0 release out of the door. The main
> features I'd like for this are,
>
> - AutoRecovery: autorerelication for ledgers in the case of bookie
> failure
> - Metastore: metadata storage, to allow other metadata backends to be
> plugged into hedwig & bookkeeper
> - Readonly bookie mode
> - Revised bookie GC
>
> The last one I'm not 100% sure about, but anything other than these
> and bugfixes should wait until 4.3.0.
>
> I'd like to try and get a first release candidate cut next week. Also,
> any help with patch reviews would be appreciated. I'm currently
> setting up automated testing for patches, which should check all the
> basic things automatically.
>
> Regards
> Ivan
>
Re: [DISCUSS] Preparation for BookKeeper 4.2.0 Release
Posted by Flavio Junqueira <fp...@yahoo-inc.com>.
Since there was no feedback, I'm also moving BOOKKEEPER-308 to 4.3.0. We have plenty of new features already.
-Flavio
On Nov 29, 2012, at 11:37 AM, Flavio Junqueira wrote:
> Should we add the JMS implementation to this release?
>
> -Flavio
>
> On Nov 23, 2012, at 4:43 PM, Ivan Kelly wrote:
>
>> Hi guys,
>>
>> Things have been progressing well lately, so I think it's time to
>> start thinking about getting 4.2.0 release out of the door. The main
>> features I'd like for this are,
>>
>> - AutoRecovery: autorerelication for ledgers in the case of bookie
>> failure
>> - Metastore: metadata storage, to allow other metadata backends to be
>> plugged into hedwig & bookkeeper
>> - Readonly bookie mode
>> - Revised bookie GC
>>
>> The last one I'm not 100% sure about, but anything other than these
>> and bugfixes should wait until 4.3.0.
>>
>> I'd like to try and get a first release candidate cut next week. Also,
>> any help with patch reviews would be appreciated. I'm currently
>> setting up automated testing for patches, which should check all the
>> basic things automatically.
>>
>> Regards
>> Ivan
>
Re: [DISCUSS] Preparation for BookKeeper 4.2.0 Release
Posted by Flavio Junqueira <fp...@yahoo-inc.com>.
Should we add the JMS implementation to this release?
-Flavio
On Nov 23, 2012, at 4:43 PM, Ivan Kelly wrote:
> Hi guys,
>
> Things have been progressing well lately, so I think it's time to
> start thinking about getting 4.2.0 release out of the door. The main
> features I'd like for this are,
>
> - AutoRecovery: autorerelication for ledgers in the case of bookie
> failure
> - Metastore: metadata storage, to allow other metadata backends to be
> plugged into hedwig & bookkeeper
> - Readonly bookie mode
> - Revised bookie GC
>
> The last one I'm not 100% sure about, but anything other than these
> and bugfixes should wait until 4.3.0.
>
> I'd like to try and get a first release candidate cut next week. Also,
> any help with patch reviews would be appreciated. I'm currently
> setting up automated testing for patches, which should check all the
> basic things automatically.
>
> Regards
> Ivan
RE: [DISCUSS] Preparation for BookKeeper 4.2.0 Release
Posted by Uma Maheswara Rao G <ma...@huawei.com>.
Thanks a lot, Ivan for the discussion and your proposal.
We also started setting up our internal CI with 4.2 (trunk), to see if any issues with Hadoop integration.
I think, it may be ok to push GC redesigning to 4.3.
Regards,
Uma
________________________________________
From: Ivan Kelly [ivank@apache.org]
Sent: Friday, November 23, 2012 9:13 PM
To: bookkeeper-dev@zookeeper.apache.org
Subject: [DISCUSS] Preparation for BookKeeper 4.2.0 Release
Hi guys,
Things have been progressing well lately, so I think it's time to
start thinking about getting 4.2.0 release out of the door. The main
features I'd like for this are,
- AutoRecovery: autorerelication for ledgers in the case of bookie
failure
- Metastore: metadata storage, to allow other metadata backends to be
plugged into hedwig & bookkeeper
- Readonly bookie mode
- Revised bookie GC
The last one I'm not 100% sure about, but anything other than these
and bugfixes should wait until 4.3.0.
I'd like to try and get a first release candidate cut next week. Also,
any help with patch reviews would be appreciated. I'm currently
setting up automated testing for patches, which should check all the
basic things automatically.
Regards
Ivan