Doug, I forgot to respond to your question about 3.4. Since 3.4 is the stable maintenance line, we are very conservative about back-porting to it. Our policy is to limit back-ports to critical bug fixes and not introduce any new features in the 3.4 line. This is a matter of managing risk.
Jason, your question about release cadence is a fair one. If it's any consolation, we are now taking the approach of trying to limit the scope of anything new introduced in 3.5 too. That would allow us to focus on stabilization: resolving blocker bugs and freezing public APIs. I think this will help us accelerate the releases into beta and eventual GA. I am new to ZooKeeper release management, so I'd like to hear thoughts from more experienced committers and PMC members about your proposal to try to cut a stable release for a limited subset of what is in branch-3.5 now. My instinct is that it would be challenging to cherry-pick out pieces of branch-3.5 piecemeal at this point. This would become another release line for an already resource-constrained volunteer staff to manage. I'd prefer to dedicate those limited resources to overall 3.5 stabilization. Also, a 3.5 release in which certain features "vanished" because of not meeting some stability criteria would be undesirable. --Chris Nauroth On 3/15/16, 10:12 AM, "Jason Rosenberg" <[email protected]> wrote: >Chris, > >Can you say whether some parts of 3.5.X are more stable than others (e.g. >if we don't care about certain new features, is it relatively stable)? >Would it be possible to cut out a version that only has the bits we think >are stable (and release that)? > >From that timeline, and the historic release cadence, it would seem to be >a >years away before we get to the stable release? > >Thanks, > >Jason > >On Tue, Mar 15, 2016 at 1:06 PM, Chris Nauroth <[email protected]> >wrote: > >> Hello Doug, >> >> Thanks for your interest in the SSL feature! >> >> At this point, I think we're still pretty far away from declaring a >>stable >> release in the 3.5 line. I don't think we're close enough that anyone >>can >> offer a reliable ETA. This is an earlier thread that describes the >> high-level strategy for release planning in the 3.5 line: >> >> https://s.apache.org/ADK1 >> >> The next step is a 3.5.2-alpha release. We're working on resolving a >>few >> more blockers before we produce a release candidate. Hopefully that >>will >> get done in the next few weeks. >> >> --Chris Nauroth >> >> >> >> >> On 3/15/16, 9:39 AM, "Doug" <[email protected]> wrote: >> >> >I know it's only been a few months, but I was wondering if there was a >> >ballpark release date for a stable version of 3.5.1. Or is there any >> >chance >> >the SSL feature would be added to 3.4.8? Just another person looking to >> >have >> >that feature in a stable version. Thanks for all you do! :) >> > >> > >> > >> >-- >> >View this message in context: >> > >> >>http://zookeeper-user.578899.n2.nabble.com/Zookeeper-with-SSL-release-dat >>e >> >-tp7581744p7582136.html >> >Sent from the zookeeper-user mailing list archive at Nabble.com. >> > >> >>
