Not missing anything. We switched to a new model in 3.5 and later. What you outlined is the new process (just go ahead and replace).
Patrick On Tue, Aug 16, 2016 at 10:56 PM, Rakesh Radhakrishnan <rake...@apache.org> wrote: > On a second look, I think I need to update the existing > 'releasenotes.html' details by manually replace the contents with the > jira for all the versions as the page formatting is different for the > existing content. Shall I convert the existing content in this file to the > new format ? Am I missing anything here? > > Rakesh > > On Wed, Aug 17, 2016 at 10:57 AM, Rakesh Radhakrishnan <rake...@apache.org > > wrote: > >> It seems, https://github.com/apache/zookeeper/blob/branch-3.4/ >> docs/releasenotes.html beginning with "ZooKeeper 3.4.5 Release Notes". I >> hope I need to append the details of 3.4.6, 3.4.7, 3.4.8 first and then add >> our current 3.4.9 release notes, isn't it? >> >> >> Thanks, >> Rakesh >> >> On Wed, Aug 17, 2016 at 8:13 AM, Rakesh Radhakrishnan <rake...@apache.org >> > wrote: >> >>> Thanks Patrick and Chris for quickly resolving this. I will continue >>> with the release procedures. >>> >>> Rakesh >>> >>> On Wed, Aug 17, 2016 at 4:50 AM, Patrick Hunt <ph...@apache.org> wrote: >>> >>>> Great, thanks Chris! >>>> >>>> Patrick >>>> >>>> On Tue, Aug 16, 2016 at 4:16 PM, Chris Nauroth < >>>> cnaur...@hortonworks.com> wrote: >>>> >>>>> I just committed the ZOOKEEPER-2514 patch. Patrick, thank you for the >>>>> quick turnaround. Rakesh, I think you’re all set to proceed with release >>>>> notes for the 3.4.9 release candidate. >>>>> >>>>> --Chris Nauroth >>>>> >>>>> On 8/16/16, 2:52 PM, "Patrick Hunt" <ph...@apache.org> wrote: >>>>> >>>>> Rakesh pointed out that the current "how to release" docs no >>>>> longer are >>>>> correct for branch-3.4 as in branch-3.5 and later we updated the >>>>> release >>>>> notes creation process to simplify it. Used to be very manual, in >>>>> 3.5+ we >>>>> moved to using the HTML available from Jira. I've created the >>>>> following >>>>> JIRA to backport that change to branch 3.4. After this patch is >>>>> applied the >>>>> RM process for release notes creation in 3.4 is consistent with >>>>> the "how to >>>>> release" documentation available on the wiki. >>>>> >>>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2514 >>>>> >>>>> Chris would you be able to take a look/review as well? That would >>>>> help to >>>>> unstick Rakesh with 3.4.9 (although he can review/commit as well >>>>> but given >>>>> the timezone diff...) >>>>> >>>>> Thanks, >>>>> >>>>> Patrick >>>>> >>>>> >>>>> On Tue, Aug 16, 2016 at 10:55 AM, Chris Nauroth < >>>>> cnaur...@hortonworks.com> >>>>> wrote: >>>>> >>>>> > +1 for the plan. Rakesh, thank you for working on the 3.4.9 >>>>> release. >>>>> > >>>>> > --Chris Nauroth >>>>> > >>>>> > On 8/15/16, 7:43 AM, "Rakesh Radhakrishnan" <rake...@apache.org> >>>>> wrote: >>>>> > >>>>> > Hi All, >>>>> > >>>>> > I think we have given enough time to push issues into 3.4.9 >>>>> version >>>>> > release. I'm planning to start looking at the jira issues >>>>> currently >>>>> > marked >>>>> > for 3.4.9 and move into 3.4.10. I'd like to propose a >>>>> deadline, >>>>> > sometime >>>>> > around *Tuesday, 16 August 2016 PST* to hear from you. Kindly >>>>> > requesting >>>>> > everyone to look at the open jira issues marked for 3.4.9 >>>>> and let me >>>>> > know >>>>> > your thoughts asap. Thanks! >>>>> > >>>>> > I personally feel, only ZOOKEEPER-2383 blocker could be good >>>>> candidate >>>>> > for >>>>> > this version. Please feel free to add your inputs and help >>>>> me to take a >>>>> > decision for this jira. >>>>> > >>>>> > Please find the open issues here, https://goo.gl/SEliwm >>>>> > >>>>> > Thanks, >>>>> > Rakesh >>>>> > >>>>> > On Sat, Jul 30, 2016 at 6:16 PM, Rakesh Radhakrishnan < >>>>> > rake...@apache.org> >>>>> > wrote: >>>>> > >>>>> > > Hi All, >>>>> > > >>>>> > > (1) ZK-2383 -> Attached patch and the bug reporter has >>>>> shown >>>>> > interests to >>>>> > > review/test the available patch. @Flavio, @Patrick, do you >>>>> have some >>>>> > cycles >>>>> > > to review the proposed patch. Welcome others input as >>>>> well. Thanks! >>>>> > > >>>>> > > (2) I believe we are very close to finish ZK-2247, waiting >>>>> for the >>>>> > final >>>>> > > reviews and commit. >>>>> > > >>>>> > > (3) I'd love to include ZK-2355 also. It looks like the >>>>> fix is good, >>>>> > I've >>>>> > > added few comments. Perhaps, will wait to see feedback >>>>> from others. >>>>> > > >>>>> > > Kindly requesting everyone to look at your issues marked >>>>> for 3.4.9 >>>>> > and >>>>> > > push these asap or can be pushed out to 3.4.10. >>>>> > > >>>>> > > Thanks, >>>>> > > Rakesh >>>>> > > >>>>> > > On Tue, Jul 19, 2016 at 2:49 AM, Patrick Hunt < >>>>> ph...@apache.org> >>>>> > wrote: >>>>> > > >>>>> > >> On Sat, Jul 9, 2016 at 10:26 AM, Rakesh Radhakrishnan >>>>> > >> <rake...@apache.org> wrote: >>>>> > >> > >>>>> > >> > >>>>>ZK-1045 is a major change and I suggest we give >>>>> time for >>>>> > folks to >>>>> > >> try >>>>> > >> > it out before cutting a release candidate. Ideally, we >>>>> check it >>>>> > in and >>>>> > >> give >>>>> > >> > a few weeks until we cut a release candidate. >>>>> > >> > >>>>> > >> > Agreed, will try to push ZK-1045 in asap. Michael and >>>>> myself is >>>>> > working >>>>> > >> > closely to finish the following set of open points. >>>>> Hopefully by >>>>> > next >>>>> > >> week >>>>> > >> > we will be able to complete the identified tasks, then >>>>> will post >>>>> > updated >>>>> > >> > patch and test report. I would appreciate review >>>>> > >> > comments/questions/feedback from others. >>>>> > >> > >>>>> > >> >>>>> > >> I am taking another pass at this next. >>>>> > >> >>>>> > >> > Pending tasks:- >>>>> > >> > 1) support authorization in sasl. >>>>> > >> > 2) few minor log improvements are open. >>>>> > >> > 3) system testing and preparing report. >>>>> > >> > 4) feature document with latest changes. >>>>> > >> > >>>>> > >> > >>>>> > >> > >>>>>The other one, ZK-2383, needs work. >>>>> > >> > >>>>> > >> > Here, I'm planning to revert ZOOKEEPER-2026 committed >>>>> code and >>>>> > makes >>>>> > >> this >>>>> > >> > issue open for discussion/fix. Does it sound good? >>>>> > >> > >>>>> > >> >>>>> > >> Given 2026 is already shipping I would be concerned about >>>>> reverting >>>>> > it >>>>> > >> at this point. Why wouldn't we just fix the remaining >>>>> issue(s)? >>>>> > >> >>>>> > >> Patrick >>>>> > >> >>>>> > >> > Thanks, >>>>> > >> > Rakesh >>>>> > >> > >>>>> > >> > On Thu, Jul 7, 2016 at 6:51 PM, Flavio Junqueira < >>>>> f...@apache.org> >>>>> > >> wrote: >>>>> > >> > >>>>> > >> > > Thanks for bootstrapping the release process for >>>>> 3.4.9. ZK-1045 >>>>> > is a >>>>> > >> major >>>>> > >> > > change and I suggest we give time for folks to try it >>>>> out before >>>>> > >> cutting a >>>>> > >> > > release candidate. Ideally, we check it in and give a >>>>> few weeks >>>>> > until >>>>> > >> we >>>>> > >> > > cut a release candidate. >>>>> > >> > > >>>>> > >> > > One of the blockers, ZK-2314 has only one remaining >>>>> task which >>>>> > is to >>>>> > >> > > document missing SASL properties, so that should be >>>>> easy. The >>>>> > other >>>>> > >> one, >>>>> > >> > > ZK-2383, needs work. >>>>> > >> > > >>>>> > >> > > Folks should check the remaining issues to determine >>>>> if there >>>>> > is any >>>>> > >> other >>>>> > >> > > blocker that we missed in that list. >>>>> > >> > > >>>>> > >> > > -Flavio >>>>> > >> > > >>>>> > >> > > > On 07 Jul 2016, at 05:12, Rakesh Radhakrishnan < >>>>> > rake...@apache.org> >>>>> > >> > > wrote: >>>>> > >> > > > >>>>> > >> > > > Hi All, >>>>> > >> > > > >>>>> > >> > > > I am interested in going through the release >>>>> process as the >>>>> > RM. >>>>> > >> > > > >>>>> > >> > > > I could see total 23 issues marked for 3.4.9 >>>>> release as of >>>>> > now, >>>>> > >> which >>>>> > >> > > > includes 2 blockers, 6 critical, 12 major and 3 >>>>> minor issues. >>>>> > I >>>>> > >> count 15 >>>>> > >> > > > issues fixed/committed already for 3.4.9 which >>>>> includes 6 >>>>> > blockers >>>>> > >> and 2 >>>>> > >> > > > critical(security related) issues. I think it is a >>>>> good time >>>>> > to >>>>> > >> initiate >>>>> > >> > > > the discussion of 3.4.9 release processes. >>>>> > >> > > > >>>>> > >> > > > Please find the open issues here, >>>>> https://goo.gl/SEliwm >>>>> > >> > > > >>>>> > >> > > > Currently, I'm focusing on ZOOKEEPER-1045 sasl >>>>> feature which I >>>>> > >> think is >>>>> > >> > > > much appreciated/awaited feature and I'd like to >>>>> include this >>>>> > if >>>>> > >> everyone >>>>> > >> > > > agrees. Appreciate help in reviewing/testing the >>>>> patch and >>>>> > making it >>>>> > >> > > stable >>>>> > >> > > > for release. Also, please feel free to push your >>>>> favorite >>>>> > issues >>>>> > >> ahead of >>>>> > >> > > > 3.4.9 release. >>>>> > >> > > > >>>>> > >> > > > I hope we should be able to close all blockers and >>>>> critical >>>>> > issues >>>>> > >> in a >>>>> > >> > > > month. Kindly requesting everyone to look at the >>>>> issues >>>>> > marked for >>>>> > >> 3.4.9 >>>>> > >> > > > and push these asap or can be pushed out to 3.4.10. >>>>> I will >>>>> > focus my >>>>> > >> code >>>>> > >> > > > review time on these. >>>>> > >> > > > >>>>> > >> > > > Please let me know your thoughts on the plan. >>>>> > >> > > > >>>>> > >> > > > Thanks, >>>>> > >> > > > Rakesh >>>>> > >> > > >>>>> > >> > > >>>>> > >> >>>>> > > >>>>> > > >>>>> > >>>>> > >>>>> > >>>>> >>>>> >>>>> >>>> >>> >> >
