Thanks for feedback, Sijie. In principle, I don't have a problem with adding any of the points you mention below, but see some comments inline:
On May 22, 2013, at 7:09 AM, Sijie Guo <[email protected]> wrote: > I think there are bunch of things left from 4.2.0 needs to be in 4.3.0. > > - skiplist based ledger storage and other improvements on bookie server > side (there was already patches in 4.2.0 release) I haven't followed the progress here very closely. How close to you think this is of getting into trunk? > - gc improvement (this is also left from 4.2.0) > - ledger id generation improvements (those patches made by Jiannan also > exists for a long time) I have to look at those jiras, but my recollection is that we haven't converged into a solution. Also, who is going to wrap them up? > - managed ledger (it also exists from 4.1.0) I also haven't seen a lot of progress with that patch, so I'm reluctant to depend upon that work for the release. What do you think? -Flavio > > -Sijie > > > > On Tue, May 21, 2013 at 5:07 PM, Flavio Junqueira > <[email protected]>wrote: > >> It is probably time to start thinking about wrapping up 4.3.0. There are 77 >> jiras marked for 4.3.0 and we have considered for this release the >> following >> features: >> >> * Security (SASL on bookie) >> * NIOServerFactory -> Netty >> >> The rack awareness work was not marked for this release, but I suppose it >> is >> ok to include it here, since the patch Sijie proposed for BOOKKEEPER-592 >> seems to be in good shape. The Netty work is in BOOKKEEPER-555, which is in >> already. We just need to work on the security part, which I think there has >> been some progress recently. At least I have seen some progress from >> Rakesh. >> >> >> >> Any thoughts about cutting a release say by mid-june? >> >> >> >> -Flavio >> >>
