Thanks for the offer Camille. Ill be going through the jira's/PA's tonight to filter the ones that can get into the 3.4.4 release. From a cursory look I think 2 weeks should be good enough but we'll have a better idea once we go through the PA's and the ones marked for 3.4.4.
Ill definitely be pinging committers for specific jira reviews by tonight. Given we have a long weekend coming, I expect folks will get some time to review :). thanks mahadev On Wed, Aug 29, 2012 at 6:00 PM, Camille Fournier <cami...@apache.org> wrote: > Can we get a more concrete date on 3.4? What can I help with this weekend > to get 3.4 ready for a new release? > > Thanks, > C > > On Sun, Aug 26, 2012 at 5:03 PM, Mahadev Konar <maha...@hortonworks.com>wrote: > >> Thanks Pat for driving the 3.3.* stable release. Apologize for my late >> response, I've been on vacation for the last couple of weeks. Ill >> take care of 3.4 release. Hopefully try to nail this down in the next >> couple of weeks. >> >> Himanshu, hopefully the above should answer your question. >> >> thanks >> mahadev >> >> On Mon, Aug 20, 2012 at 11:20 AM, Himanshu Vashishtha >> <himan...@cloudera.com> wrote: >> > yeah, by 3.4, I meant "stable 3.4.4" :) >> > >> > On Mon, Aug 20, 2012 at 12:18 PM, Himanshu Vashishtha < >> himan...@cloudera.com >> >> wrote: >> > >> >> Hello Devs, >> >> >> >> I am also interested in knowing the status of 3.4 release, its possible >> >> release date and will it be labelled as *stable*? >> >> There are some important HBase jiras that can make use of the #multi >> >> support in 3.4 (such as HBase-2611). >> >> >> >> Looking forward for a stable 3.4 release. >> >> >> >> Thanks, >> >> Himanshu >> >> >> >> >> >> >> >> On Mon, Aug 20, 2012 at 12:09 PM, Patrick Hunt <ph...@apache.org> >> wrote: >> >> >> >>> 3.3.6 is now live so we should turn our attention to 3.4.4. Mahadev do >> >>> you still want to drive the 3.4.4 release? >> >>> >> >>> afaict there are 4 PA's, one of which is the SASL issue Eugene has >> >>> been diligently working on. Would be great if we could nail these down >> >>> asap. >> >>> >> >>> Patrick >> >>> >> >>> On Thu, Jul 12, 2012 at 9:34 AM, Patrick Hunt <ph...@apache.org> >> wrote: >> >>> > We've made good progress. 1489 tests are now passing consistently and >> >>> > the patch is about to be committed, which means that 3.3.6 is >> >>> > unblocked. >> >>> > >> >>> > I'd like to get Michi's patch in, it's the only other PA remaining on >> >>> > 3.3.6, can someone review this asap? >> >>> > https://issues.apache.org/jira/browse/ZOOKEEPER-1493 >> >>> > >> >>> > I'll cut a 3.3.6 release candidate as soon as these two jira are >> >>> finalized. >> >>> > >> >>> > On the 3.4.4 front there is just one blocker left - 1489. >> >>> > >> >>> > 1427 is ready to be committed. There are some other PA's for 3.4.4 >> >>> > that I'd like to see get in. In particular the SASL fix >> >>> > (https://issues.apache.org/jira/browse/ZOOKEEPER-1437), if someone >> can >> >>> > work with Eugene to finalize this it would be great. Anyone? >> >>> > >> >>> > Patrick >> >>> > >> >>> > On Fri, Jul 6, 2012 at 2:20 PM, Patrick Hunt <ph...@apache.org> >> wrote: >> >>> >> It was that way in the original code. I kept it because it was >> easier >> >>> >> to see when running in eclipse, etc... Given it all goes to the log >> >>> >> file I didn't see a problem, but I'm fine to move it to logging. LMK >> >>> >> if you think I should, otw I'll leave as-is. >> >>> >> >> >>> >> Patrick >> >>> >> >> >>> >> On Fri, Jul 6, 2012 at 1:35 PM, Camille Fournier < >> cami...@apache.org> >> >>> wrote: >> >>> >>> Looking at 1489... Are we putting printlns in tests now? I can't >> >>> remember >> >>> >>> if that's kosher or not. >> >>> >>> >> >>> >>> C >> >>> >>> >> >>> >>> On Fri, Jul 6, 2012 at 12:26 PM, Patrick Hunt <ph...@apache.org> >> >>> wrote: >> >>> >>> >> >>> >>>> There's one blocker left covering both 3.3.6 and 3.4.4: >> >>> >>>> https://issues.apache.org/jira/browse/ZOOKEEPER-1489 >> >>> >>>> Also the sasl auth and atomic epoch file creation would be good to >> >>> get in. >> >>> >>>> https://issues.apache.org/jira/browse/ZOOKEEPER-1437 >> >>> >>>> https://issues.apache.org/jira/browse/ZOOKEEPER-1427 >> >>> >>>> >> >>> >>>> if anyone has time to review these please do (two are mine so I >> >>> can't ;-) ) >> >>> >>>> >> >>> >>>> additionally the sasl change touches critical codepaths in the >> >>> client, >> >>> >>>> would be good to get more eyes on that. >> >>> >>>> >> >>> >>>> Once these are in we should be able to create an rc. >> >>> >>>> >> >>> >>>> Regards, >> >>> >>>> >> >>> >>>> Patrick >> >>> >>>> >> >>> >>>> On Fri, Jun 29, 2012 at 11:42 AM, Eugene Koontz < >> >>> ekoo...@hiro-tan.org> >> >>> >>>> wrote: >> >>> >>>> > On 6/29/12 10:35 AM, Patrick Hunt wrote: >> >>> >>>> >> Mahadev and I were discussing that we should plan for 3.3.6 and >> >>> 3.4.4 >> >>> >>>> >> releases soon. Primarily to incorporate the SASL fix and the >> log >> >>> >>>> >> truncation fix. I don't see much pressing for the rest of the >> >>> pending >> >>> >>>> >> jiras. >> >>> >>>> >> >> >>> >>>> >> https://issues.apache.org/jira/browse/ZOOKEEPER-1489 >> >>> >>>> >> https://issues.apache.org/jira/browse/ZOOKEEPER-1437 >> >>> >>>> >> >> >>> >>>> >> Let's plan for a release candidate next week, or early the >> >>> following. >> >>> >>>> >> We should try and burn down the PA queue, esp for things slated >> >>> for >> >>> >>>> >> 3.3.6/3.4.4. If there's something critical that should be on >> the >> >>> list >> >>> >>>> >> please speak up. (you'll probably see me/Mahadev triaging the >> jira >> >>> >>>> >> lists over the coming days) >> >>> >>>> >> >> >>> >>>> >> Based on community feedback we'll mark 3.4.4 as "stable". >> >>> >>>> >> >> >>> >>>> >> Patrick >> >>> >>>> >> >> >>> >>>> > >> >>> >>>> > This is great to hear - I'm looking forward to helping get >> >>> >>>> > ZOOKEEPER-1437 released in 3.4.4. >> >>> >>>> > -Eugene >> >>> >>>> >> >>> >> >> >> >> >>
