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
wrote:
> On a second look, I think I need to update the existing
>
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
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
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 wrote:
> Great, thanks Chris!
>
> Patrick
>
> On Tue, Aug 16, 2016 at 4:16 PM, Chris Nauroth
>
Great, thanks Chris!
Patrick
On Tue, Aug 16, 2016 at 4:16 PM, Chris Nauroth
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
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" wrote:
Rakesh pointed out that the
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
+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" 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
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
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
On Sat, Jul 9, 2016 at 10:26 AM, Rakesh Radhakrishnan
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,
>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
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
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
14 matches
Mail list logo