You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Andor Molnar <an...@cloudera.com> on 2018/03/02 00:38:41 UTC
3.4.12
Hi dev,
User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
<https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?)
Are we good to cut 3.4.12 soon or still waiting for something to be
committed?
Andor
Re: 3.4.12
Posted by Abraham Fine <af...@apache.org>.
Thank's Pat.
I'll get started on this ASAP.
On Mon, Mar 5, 2018, at 10:14, Patrick Hunt wrote:
> Thanks for "volunteering" Abe. :-)
>
> sgtm, +1 - there are some important fixes to get out for 3.4.
>
> FYI the "how to release" page is here:
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease+using+git
> ff to ping me if you run into issues (update that page if you do find
> issues)
>
> Regards,
>
> Patrick
>
> On Fri, Mar 2, 2018 at 2:49 PM, Abraham Fine <af...@apache.org> wrote:
>
> > I am very much interested in taking a turn as a RM and I think it is a
> > great time to do a release (now that 2967, 2249, and 2960 arge merged in).
> >
> > I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is
> > anything else that we need to merge in before cutting a release.
> >
> > Abe
> >
> > On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
> > > There are 19 resolved issues http://bit.ly/2oK9aTx
> > > and 14 unresolved http://bit.ly/2oFWywS
> > > ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
> > > regression and was pushed from 3.4.11, we could do so again given it's
> > > still being worked on.
> > >
> > > Abe are you interested in taking a turn as RM?
> > >
> > > Patrick
> > >
> > > On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote:
> > >
> > > > Hi dev,
> > > >
> > > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> > > > <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?)
> > > > Are we good to cut 3.4.12 soon or still waiting for something to be
> > > > committed?
> > > >
> > > > Andor
> > > >
> >
Re: 3.4.12
Posted by Patrick Hunt <ph...@apache.org>.
Thanks for "volunteering" Abe. :-)
sgtm, +1 - there are some important fixes to get out for 3.4.
FYI the "how to release" page is here:
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease+using+git
ff to ping me if you run into issues (update that page if you do find
issues)
Regards,
Patrick
On Fri, Mar 2, 2018 at 2:49 PM, Abraham Fine <af...@apache.org> wrote:
> I am very much interested in taking a turn as a RM and I think it is a
> great time to do a release (now that 2967, 2249, and 2960 arge merged in).
>
> I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is
> anything else that we need to merge in before cutting a release.
>
> Abe
>
> On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
> > There are 19 resolved issues http://bit.ly/2oK9aTx
> > and 14 unresolved http://bit.ly/2oFWywS
> > ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
> > regression and was pushed from 3.4.11, we could do so again given it's
> > still being worked on.
> >
> > Abe are you interested in taking a turn as RM?
> >
> > Patrick
> >
> > On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote:
> >
> > > Hi dev,
> > >
> > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> > > <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?)
> > > Are we good to cut 3.4.12 soon or still waiting for something to be
> > > committed?
> > >
> > > Andor
> > >
>
Re: 3.4.12
Posted by Flavio Junqueira <fp...@apache.org>.
+1 for cutting a 3.4.12 RC. Thanks for volunteering, Abe.
-Flavio
> On 8 Mar 2018, at 18:53, Rakesh Radhakrishnan <ra...@apache.org> wrote:
>
> Appreciate Abe for the initiative and efforts!
>
> +1, for "3.4.12" releasing.
>
> Please feel free to ping me if any help needed when making this release.
>
> Regards,
> Rakesh
>
> On Sat, Mar 3, 2018 at 4:19 AM, Abraham Fine <af...@apache.org> wrote:
>
>> I am very much interested in taking a turn as a RM and I think it is a
>> great time to do a release (now that 2967, 2249, and 2960 arge merged in).
>>
>> I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is
>> anything else that we need to merge in before cutting a release.
>>
>> Abe
>>
>> On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
>>> There are 19 resolved issues http://bit.ly/2oK9aTx
>>> and 14 unresolved http://bit.ly/2oFWywS
>>> ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
>>> regression and was pushed from 3.4.11, we could do so again given it's
>>> still being worked on.
>>>
>>> Abe are you interested in taking a turn as RM?
>>>
>>> Patrick
>>>
>>> On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote:
>>>
>>>> Hi dev,
>>>>
>>>> User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
>>>> <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?)
>>>> Are we good to cut 3.4.12 soon or still waiting for something to be
>>>> committed?
>>>>
>>>> Andor
>>>>
>>
Re: 3.4.12
Posted by Rakesh Radhakrishnan <ra...@apache.org>.
Appreciate Abe for the initiative and efforts!
+1, for "3.4.12" releasing.
Please feel free to ping me if any help needed when making this release.
Regards,
Rakesh
On Sat, Mar 3, 2018 at 4:19 AM, Abraham Fine <af...@apache.org> wrote:
> I am very much interested in taking a turn as a RM and I think it is a
> great time to do a release (now that 2967, 2249, and 2960 arge merged in).
>
> I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is
> anything else that we need to merge in before cutting a release.
>
> Abe
>
> On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
> > There are 19 resolved issues http://bit.ly/2oK9aTx
> > and 14 unresolved http://bit.ly/2oFWywS
> > ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
> > regression and was pushed from 3.4.11, we could do so again given it's
> > still being worked on.
> >
> > Abe are you interested in taking a turn as RM?
> >
> > Patrick
> >
> > On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote:
> >
> > > Hi dev,
> > >
> > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> > > <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?)
> > > Are we good to cut 3.4.12 soon or still waiting for something to be
> > > committed?
> > >
> > > Andor
> > >
>
Re: 3.4.12
Posted by Abraham Fine <af...@apache.org>.
I am very much interested in taking a turn as a RM and I think it is a great time to do a release (now that 2967, 2249, and 2960 arge merged in).
I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is anything else that we need to merge in before cutting a release.
Abe
On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
> There are 19 resolved issues http://bit.ly/2oK9aTx
> and 14 unresolved http://bit.ly/2oFWywS
> ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
> regression and was pushed from 3.4.11, we could do so again given it's
> still being worked on.
>
> Abe are you interested in taking a turn as RM?
>
> Patrick
>
> On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote:
>
> > Hi dev,
> >
> > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> > <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?)
> > Are we good to cut 3.4.12 soon or still waiting for something to be
> > committed?
> >
> > Andor
> >
Re: 3.4.12
Posted by Patrick Hunt <ph...@apache.org>.
There are 19 resolved issues http://bit.ly/2oK9aTx
and 14 unresolved http://bit.ly/2oFWywS
ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
regression and was pushed from 3.4.11, we could do so again given it's
still being worked on.
Abe are you interested in taking a turn as RM?
Patrick
On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar <an...@cloudera.com> wrote:
> Hi dev,
>
> User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> <https://issues.apache.org/jira/browse/ZOOKEEPER-2960>) (again?)
> Are we good to cut 3.4.12 soon or still waiting for something to be
> committed?
>
> Andor
>