Sounds like a great plan. There is a patch available for review for flaky startSingleServerTest.
https://issues.apache.org/jira/browse/ZOOKEEPER-1870 On Tue, Apr 8, 2014 at 10:12 PM, Patrick Hunt <[email protected]> wrote: > I see some great progress in closing out jiras. Kudos all. We > currently have 12 blockers for 3.5.0, 5 are listed as PA. Let's keep > plugging away on these. > > The CI environment has gone a bit red of late. On my personal servers > I'm seeing it mostly in "startSingleServerTest" though, so perhaps > it's localized. Would be good to nail down the flakey tests. I'll try > looking into this more (what the flakeys are) and report back. Apache > CI seems a bit unstable of late (the jenkins env I mean) > > I'm thinking we might start creating some Alpha releases, e.g. > zookeeper-3.5.0-alpha so that we can get the code into folks hands. > They can try it out and give us feedback. It would be alpha quality > though, not for production. APIs and new functionality might still > change in a non-backward compatible way. We could do this even though > we still have some blockers remaining. Once all the blockers are > resolved we could move to "beta" status. The APIs, etc... would then > be locked. Once things settle out during the beta cycle we could then > move off "beta". We'd only make 3.5 "stable" once we feel comfortable > with it's quality and after collecting feedback from the community. > This is basically what we did for 3.4 branch (and similar to what some > other projects do). What do you think? > > Patrick > > On Thu, Apr 3, 2014 at 5:33 PM, Michi Mutsuzaki <[email protected]> wrote: >> ... there is one more. I just canceled it because the patch needs to be >> rebased. >> >> https://issues.apache.org/jira/browse/ZOOKEEPER-1794 >> >> On Thu, Apr 3, 2014 at 5:31 PM, Michi Mutsuzaki <[email protected]> >> wrote: >>> There are several large PAs: >>> >>> https://issues.apache.org/jira/browse/ZOOKEEPER-1172 >>> https://issues.apache.org/jira/browse/ZOOKEEPER-1346 >>> https://issues.apache.org/jira/browse/ZOOKEEPER-1607 >>> https://issues.apache.org/jira/browse/ZOOKEEPER-1907 >>> >>> >>> I think I can review ZOOKEEPER-1907 and get it in for 3.5.0, but we >>> need shepherds for the other 3 JIRAs. Let me know if anybody has >>> cycles to review and check in these patches. Otherwise I'll push them >>> out of 3.5.0. >>> >>> Thanks! >>> --Michi >>> >>> On Thu, Mar 20, 2014 at 1:56 PM, Alexander Shraer <[email protected]> wrote: >>>> right - looks like there's a patch there, waiting for review. >>>> >>>> >>>> On Thu, Mar 20, 2014 at 1:52 PM, Raúl Gutiérrez Segalés >>>> <[email protected] >>>>> wrote: >>>> >>>>> On 20 March 2014 13:51, Raúl Gutiérrez Segalés <[email protected]> >>>>> wrote: >>>>> >>>>> > what about https://issues.apache.org/jira/browse/ZOOKEEPER-1807? >>>>> > >>>>> >>>>> More context: people trying to use Observers in 3.5.0 without that fixed >>>>> will have issues, for sure. >>>>> >>>>> >>>>> -rgs >>>>> >>>>> >>>>> >>>>> > >>>>> > >>>>> > -rgs >>>>> > >>>>> > >>>>> > On 20 March 2014 13:48, Alexander Shraer <[email protected]> wrote: >>>>> > >>>>> >> thanks Patrick! >>>>> >> >>>>> >> regarding dynamic reconfig, IMHO we only have 2 blockers: >>>>> >> - add JMX support >>>>> >> (ZOOKEEPER-1659<https://issues.apache.org/jira/browse/ZOOKEEPER-1659> >>>>> >> ) >>>>> >> - change leader timeout mechanism to give up when there's no quorum of >>>>> >> last >>>>> >> proposed configuration >>>>> >> (ZOOKEEPER-1699<https://issues.apache.org/jira/browse/ZOOKEEPER-1699> >>>>> >> ) >>>>> >> >>>>> >> any help with either is greatly appreciated. >>>>> >> >>>>> >> On Thu, Mar 20, 2014 at 1:32 PM, Patrick Hunt <[email protected]> wrote: >>>>> >> >>>>> >> > I'm resurrecting this thread now that 3.4.6 is out the door. I'm >>>>> >> > assuming that we might do a 3.4.7 at some point, but that shouldn't >>>>> >> > hold up releasing a 3.5.0. >>>>> >> > >>>>> >> > We discussed a number of good ideas previously in this thread wrt >>>>> >> > what >>>>> >> > we should do for 3.5.0. Any further thoughts? >>>>> >> > >>>>> >> > A big part of the planning will be to clean up Jira and figuring out >>>>> >> > what we need to finish. I'll start looking at that but if anyone else >>>>> >> > has any ideas of can clean up jiras they are familiar with it would >>>>> >> > be >>>>> >> > helpful. >>>>> >> > >>>>> >> > Here's the list currently slated for 3.5.0 (258 total!): >>>>> >> > http://bit.ly/1ijYAJF >>>>> >> > >>>>> >> > There are 8 listed blockers at the moment. Most of which have to do >>>>> >> > with the introduction of dynamic reconfiguration. Only one jira is >>>>> >> > PA. >>>>> >> > >>>>> >> > There are 52 PA jiras currently slated for 3.5.0: >>>>> http://bit.ly/PV21NA >>>>> >> > >>>>> >> > Patrick >>>>> >> > >>>>> >> > On Wed, Jul 10, 2013 at 1:38 PM, Flavio Junqueira < >>>>> >> [email protected]> >>>>> >> > wrote: >>>>> >> > > Sure, fine with me. >>>>> >> > > >>>>> >> > > -Flavio >>>>> >> > > >>>>> >> > > On Jul 10, 2013, at 7:31 PM, Mahadev Konar <[email protected] >>>>> > >>>>> >> > wrote: >>>>> >> > > >>>>> >> > >> It would be good if Flavio wants to try doing the RM. Flavio? >>>>> >> > >> >>>>> >> > >> thanks >>>>> >> > >> mahadev >>>>> >> > >> >>>>> >> > >> On Wed, Jul 10, 2013 at 10:20 AM, Patrick Hunt <[email protected]> >>>>> >> > wrote: >>>>> >> > >>> Mahadev do you want to RM 3.4.6 or should Flavio try his hand at >>>>> >> doing >>>>> >> > >>> a release? >>>>> >> > >>> >>>>> >> > >>> Patrick >>>>> >> > >>> >>>>> >> > >>> On Wed, Jul 10, 2013 at 9:50 AM, Mahadev Konar < >>>>> >> > [email protected]> wrote: >>>>> >> > >>>> 1147 is pretty close. I am working on getting this into trunk. >>>>> >> > >>>> >>>>> >> > >>>> Hopefully today/tomm. >>>>> >> > >>>> >>>>> >> > >>>> thanks >>>>> >> > >>>> mahadev >>>>> >> > >>>> >>>>> >> > >>>> On Wed, Jul 10, 2013 at 7:01 AM, Flavio Junqueira < >>>>> >> > [email protected]> wrote: >>>>> >> > >>>>> I've also been wondering about 3.4.6. I don't mind being the RM >>>>> >> for >>>>> >> > 3.5.0 if you want to do 3.4.6. >>>>> >> > >>>>> >>>>> >> > >>>>> -Flavio >>>>> >> > >>>>> >>>>> >> > >>>>> On Jul 9, 2013, at 5:49 PM, Patrick Hunt <[email protected]> >>>>> >> wrote: >>>>> >> > >>>>> >>>>> >> > >>>>>> I'd like to see a 3.5.0-alpha soon. I agree re 1147 and iirc >>>>> >> > >>>>>> it >>>>> >> was >>>>> >> > >>>>>> pretty close (Mahadev?). ZOOKEEPER-1346 (jetty support for >>>>> >> > monitoring) >>>>> >> > >>>>>> should also go in. It's pretty much ready afair. >>>>> >> > >>>>>> >>>>> >> > >>>>>> I'm happy to RM 3.5 if we can get past these open issues. >>>>> >> > >>>>>> >>>>> >> > >>>>>> Patrick >>>>> >> > >>>>>> >>>>> >> > >>>>>> >>>>> >> > >>>>>> On Tue, Jul 9, 2013 at 8:32 AM, Raúl Gutiérrez Segalés >>>>> >> > >>>>>> <[email protected]> wrote: >>>>> >> > >>>>>>> Hi Stefan, >>>>> >> > >>>>>>> >>>>> >> > >>>>>>> On 9 July 2013 08:13, Stefan Egli <[email protected]> wrote: >>>>> >> > >>>>>>>> Hi, >>>>> >> > >>>>>>>> >>>>> >> > >>>>>>>> We're evaluating using ZooKeeper, and esp the embedded mode >>>>> >> > (ZOOKEEPER-107 - [0]), for an implementation of the Sling Discovery >>>>> API >>>>> >> > ([1]). Since ZOOKEEPER-107 is planned for 3.5.0 I was wondering what >>>>> the >>>>> >> > release schedule of 3.5.0 is, or any plan thereof? (I saw a >>>>> >> > discussion >>>>> >> > about releasing it from Dec 2012 [1]). >>>>> >> > >>>>>>>> >>>>> >> > >>>>>>> >>>>> >> > >>>>>>> I think as of now the biggest blocker is: >>>>> >> > >>>>>>> >>>>> >> > >>>>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-1147 >>>>> >> > >>>>>>> >>>>> >> > >>>>>>> Besides needing a final review it needs better documentation >>>>> >> and an >>>>> >> > >>>>>>> extra small patch (I proposed one) to support rolling updates >>>>> >> when >>>>> >> > >>>>>>> enabling local sessions. >>>>> >> > >>>>>>> >>>>> >> > >>>>>>> Cheers, >>>>> >> > >>>>>>> -rgs >>>>> >> > >>>>> >>>>> >> > > >>>>> >> > >>>>> >> >>>>> > >>>>> > >>>>>
