Hi All, I hope to cut an RC in a week - giving some more time for your favorite outstanding blocker/critical issues. Will start moving out any tickets that are not blockers and/or won’t fit the timeline - there are 1 blocker, 5 critical, 15 major, 7 minor tickets outstanding as of now. Appreciate your support in releasing 3.4.10 version. Thanks!
Please find the open issues marked for 3.4.10 release here, https://goo.gl/XdraFA Thanks, Rakesh On Tue, Dec 6, 2016 at 4:15 PM, Rakesh Radhakrishnan <[email protected]> wrote: > Hi All, > > I am interested in going through the release process as the RM. > > Overall, I could see total 41 issues marked for 3.4.10 release as of now, > which includes 4 blockers, 5 critical, 20 major and 12 minor issues. I > count 9 issues fixed/committed already for 3.4.10 which includes 1 blocker > and 1 critical(security related) issue. ZOOKEEPER-1045 is a much awaited > one and the feature code is committed. I think it is a good time to > initiate the discussion of 3.4.10 release processes. > > Please find the issues marked for 3.4.10 release here, > https://goo.gl/FfbpVG > > Currently, I'm focusing on updating ZOOKEEPER-1045 feature details into > our project cwiki and related ZOOKEEPER-2479 improvement jira. I'd like to > include ZOOKEEPER-2383 into this release if everyone agrees. Appreciate > your help in reviewing the jira patches and making it stable for release. > Also, please feel free to push your favorite issues ahead of 3.4.10 release. > > I hope with the community support, we should be able to close all > necessary blockers/critical issues soon. Kindly requesting everyone to look > at the issues marked for 3.4.10 and push these asap or can be pushed out to > 3.4.11. > > Imp: Since we moved to github repository, the release procedure > https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease > requires changes. Appreciate your help in this part. Thanks! > > Please let me know your thoughts on the plan. > > Thanks, > Rakesh >
