I've had a chance to do a cursory first review of ZOOKEEPER-2024 (major 
throughput improvement with mixed workloads).  Big thanks to Kfir for authoring 
the patch and Alex for championing it.  It's very interesting.

At this point, as release manager for 3.5.2-alpha, I am leaning towards not 
including it in this release.  This is not so much a statement on this patch 
itself as it is an acknowledgment of competing priorities.  We still have a 
fair number of blocker bugs targeted to 3.5.2-alpha.  I expect we're all going 
to need to focus on those blockers now in order to get a release ready in the 
next several weeks.

I think the feature is very compelling though.  I would like us to seriously 
consider including it before 3.5 GA.  I don't see any compatibility concerns in 
the patch, so that should make it easy to include the patch later.

Somewhat related to that, I'd like to see if we can move faster on a 3.5.3 
release after 3.5.2.  Recent mailing list discussions indicate that the 
community would like to see a quicker release cadence.  Perhaps 3.5.3 can focus 
on ZOOKEEPER-2024, API stability, and a handful of further blockers.

--Chris Nauroth

Reply via email to