I think having a release sooner than late July would be great (esp. since I don't really care about security, but some of the other work that has been done would be great to have.)
Just my 2c though. On Thu, May 23, 2013 at 11:57 AM, Flavio Junqueira <[email protected]>wrote: > I also would rather releases sooner, but we need to reach agreement on what > the release will contain. The release manager essentially decides where to > cut. Do we have a release manager for 4.3.0 already or that is still open? > > For 4.3.0, we have promised security for release 4.3.0, so I think we need > to have at least that. Some of the other features, like 592, are ready to > get in, so we don't expect them to be in the way. The other jiras depend on > the reporters to stepping up and saying if they need to be in and find > someone to wrap up the work. > > As for having 4.2.2, we tend to use the last digit for bug fix releases, > perhaps including some updates. This next release will have more than bug > fixes. > > It sounds like you'd like us to have a release sooner, yes? > > -Flavio > > ----Original Message----- > From: Whitney Sorenson [mailto:[email protected]] > Sent: 23 May 2013 15:30 > To: [email protected] > Subject: Re: [DISCUSS] Release 4.3.0 > > As an outside stakeholder, I am curious if anyone has considered dividing > up > these releases since there hasn't been a release in a while. > > For the sake of shipping something sooner rather than continuing to append > new features and ideas, what do you guys think about doing a 4.2.2 as an > intermediate? > > If it's an unreasonable suggestion, I understand completely. > > -Whitney > > > > On Thu, May 23, 2013 at 6:49 AM, Flavio Junqueira > <[email protected]>wrote: > > > This is a summary according to my understanding of the discussion so far: > > > > BOOKKEEPER-575: Bookie SSL support (umbrella jira) > > BOOKKEEPER-XXX: Provide support for bookie authentication > > BOOKKEEPER-390: Provide support for zookeeper authentication > > BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10 > > characters max, which fundamentally limits them at 9 billion > > BOOKKEEPER-590: Another Scan-And-Compare GC Implementation > > BOOKKEEPER-592: allow application to recommend ledger data locality > > (ready to go) > > BOOKKEEPER-432: Improve performance of entry log range read per ledger > > entries > > BOOKKEEPER-220: Managed ledger (optional, but nice to have) > > > > Are these the core jiras we need to resolve for 4.3.0? > > > > -Flavio > > > > -----Original Message----- > > From: Ivan Kelly [mailto:[email protected]] > > Sent: 22 May 2013 14:43 > > To: [email protected] > > Subject: Re: [DISCUSS] Release 4.3.0 > > > > > > > > [fpj] Is there a jira for the SASL work? Do happen to know all jiras > > > related to security we need to address? > > There's no JIRA for sasl or auth yet. SSL is > > https://issues.apache.org/jira/browse/BOOKKEEPER-575 > > > > > > > - skiplist based ledger storage and other improvements on bookie > > server > > > > > side (there was already patches in 4.2.0 release) > > > > This is pretty close to ready. It needs some testing though. I'll > > > > try to > > > get a set of tests carved > > > > out by the end of the week. For 4.3.0 this will be disabled by > > > > default in > > > any case. > > > > > > [fpj] What's the jira or umbrella jira for this one? > > BOOKKEEPER-432 > > > > -Ivan > > > > > >
