4.3.0. For 4.2.2 the release process shouldn't take more than an hour or two.
-Ivan On Fri, May 31, 2013 at 12:19:38PM +0200, Flavio Junqueira wrote: > I was referring to 4.3.0, since you've been the release manager for the 4.2 > branch. Are you referring to 4.3.0 or 4.2.2? > > -Flavio > > On May 31, 2013, at 12:07 PM, Ivan Kelly <[email protected]> wrote: > > > +1. I don't have time to do a release for the next few weeks. > > > > -Ivan > > > > On Fri, May 31, 2013 at 11:22:48AM +0200, Flavio Junqueira wrote: > >> I didn't get an answer to my question about the release manager. If no one > >> else volunteers, I volunteer to be the release manager. > >> > >> -Flavio > >> > >> On May 24, 2013, at 7:11 PM, Ivan Kelly <[email protected]> wrote: > >> > >>> On Thu, May 23, 2013 at 11:49:44AM +0100, Flavio Junqueira wrote: > >>>> 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? > >>> Pretty much. > >>> > >>> -Ivan > >> >
