You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Enrico Olivelli <eo...@gmail.com> on 2020/10/07 10:04:13 UTC
Re: ZooKeeper 3.7 timeline? C SASL backport?
Sorry Damien,
I thought I had answered to you but my message was never sent :-(
I think that master branch is in very good shape and we had feedback from
users about 3.6.x, in fact we already released 3.6.1 and 3.6.2.
Cutting 3.7.0 will also be a sign that the current "stable" version is
3.6., and this is very good.
Let's see if any committer volunteers to cut the release.
I will have time by the end of the month if no one else is available
Enrico
Il giorno mer 7 ott 2020 alle ore 11:01 Damien Diederen <
ddiederen@sinenomine.net> ha scritto:
>
> Hello, everybody.
>
> Would you have any feedback on this?
>
> Cheers, -D
>
>
>
> Damien Diederen <dd...@sinenomine.net> writes:
> > Greetings, all,
> >
> > I haven't initially tried to get the C SASL patches integrated in the
> > 3.6 branch, as they were not very mature and as I had noticed the
> > increased release cadence in the project.
> >
> > But I am now wondering: do we already have a time horizon for ZooKeeper
> > 3.7? Or are we waiting for a sufficient number of features to
> > "accumulate" in master?
> >
> > (I understand that each branch causes additional overhead, and that we
> > may not want to have a long ladder of cherry-picks for each patch coming
> > in.)
> >
> > In case there aren't any short-term plans, I would like to backport the
> > C and Perl SASL patches to 3.6, as they've now matured a fair bit and as
> > those patches shouldn't impact the rest of the system.
> >
> > What do you think?
> >
> > Cheers, -D
>
Re: ZooKeeper 3.7 timeline? C SASL backport?
Posted by Damien Diederen <dd...@sinenomine.net>.
Hi Enrico, all,
>> Enrico: Excellent! I'm not committer, but am happy to help.
>
> It looks like you are now able to put the release together :-)
Indeed; I was thinking about it. Not sure what's best: to start with
3.5.9, or a future 3.7.0? (I guess I'll need some hand holding either
way :)
Cheers, -D
Re: ZooKeeper 3.7 timeline? C SASL backport?
Posted by Enrico Olivelli <eo...@gmail.com>.
Damien,
Il giorno lun 12 ott 2020 alle ore 19:18 Damien Diederen <
ddiederen@sinenomine.net> ha scritto:
>
> Hi Enrico, Tamaas, all,
>
> Enrico: Excellent! I'm not committer, but am happy to help.
>
It looks like you are now able to put the release together :-)
Enrico
>
> Tamaas: Looks like you have patches which are in good shape for these
> two tickets.
>
> I am wondering about ZOOKEEPER-3301 (Enforce the quota limit): Justin,
> is something specific blocking your pull request, or is it just a matter
> of finding time to work on it? Is there a way I can help? It would be
> great to push this topic over the hump (it started with ZOOKEEPER-451!).
>
> Cheers, -D
>
>
>
>
>
> Tamas Penzes <ta...@cloudera.com.INVALID> writes:
> > Hi All,
> >
> > Let me add my two cents.
> > As I have done some cleanups and version updates recently I'd like to get
> > the following changes in 3.7:
> >
> > - ZOOKEEPER-3956
> > - ZOOKEEPER-3958
> >
> > These are the ones already waiting for review/commit and I think they
> would
> > worth to get in before someone cuts a release.
> >
> > Thanks, Tamaas
> >
> > On Wed, Oct 7, 2020 at 12:04 PM Enrico Olivelli <eo...@gmail.com>
> wrote:
> >
> >> Sorry Damien,
> >> I thought I had answered to you but my message was never sent :-(
> >>
> >> I think that master branch is in very good shape and we had feedback
> from
> >> users about 3.6.x, in fact we already released 3.6.1 and 3.6.2.
> >>
> >> Cutting 3.7.0 will also be a sign that the current "stable" version is
> >> 3.6., and this is very good.
> >>
> >> Let's see if any committer volunteers to cut the release.
> >> I will have time by the end of the month if no one else is available
> >>
> >> Enrico
> >>
> >>
> >> Il giorno mer 7 ott 2020 alle ore 11:01 Damien Diederen <
> >> ddiederen@sinenomine.net> ha scritto:
> >>
> >> >
> >> > Hello, everybody.
> >> >
> >> > Would you have any feedback on this?
> >> >
> >> > Cheers, -D
> >> >
> >> >
> >> >
> >> > Damien Diederen <dd...@sinenomine.net> writes:
> >> > > Greetings, all,
> >> > >
> >> > > I haven't initially tried to get the C SASL patches integrated in
> the
> >> > > 3.6 branch, as they were not very mature and as I had noticed the
> >> > > increased release cadence in the project.
> >> > >
> >> > > But I am now wondering: do we already have a time horizon for
> ZooKeeper
> >> > > 3.7? Or are we waiting for a sufficient number of features to
> >> > > "accumulate" in master?
> >> > >
> >> > > (I understand that each branch causes additional overhead, and that
> we
> >> > > may not want to have a long ladder of cherry-picks for each patch
> >> coming
> >> > > in.)
> >> > >
> >> > > In case there aren't any short-term plans, I would like to backport
> the
> >> > > C and Perl SASL patches to 3.6, as they've now matured a fair bit
> and
> >> as
> >> > > those patches shouldn't impact the rest of the system.
> >> > >
> >> > > What do you think?
> >> > >
> >> > > Cheers, -D
> >> >
> >>
>
Re: ZooKeeper 3.7 timeline? C SASL backport?
Posted by Damien Diederen <dd...@sinenomine.net>.
Hi Enrico, Tamaas, all,
Enrico: Excellent! I'm not committer, but am happy to help.
Tamaas: Looks like you have patches which are in good shape for these
two tickets.
I am wondering about ZOOKEEPER-3301 (Enforce the quota limit): Justin,
is something specific blocking your pull request, or is it just a matter
of finding time to work on it? Is there a way I can help? It would be
great to push this topic over the hump (it started with ZOOKEEPER-451!).
Cheers, -D
Tamas Penzes <ta...@cloudera.com.INVALID> writes:
> Hi All,
>
> Let me add my two cents.
> As I have done some cleanups and version updates recently I'd like to get
> the following changes in 3.7:
>
> - ZOOKEEPER-3956
> - ZOOKEEPER-3958
>
> These are the ones already waiting for review/commit and I think they would
> worth to get in before someone cuts a release.
>
> Thanks, Tamaas
>
> On Wed, Oct 7, 2020 at 12:04 PM Enrico Olivelli <eo...@gmail.com> wrote:
>
>> Sorry Damien,
>> I thought I had answered to you but my message was never sent :-(
>>
>> I think that master branch is in very good shape and we had feedback from
>> users about 3.6.x, in fact we already released 3.6.1 and 3.6.2.
>>
>> Cutting 3.7.0 will also be a sign that the current "stable" version is
>> 3.6., and this is very good.
>>
>> Let's see if any committer volunteers to cut the release.
>> I will have time by the end of the month if no one else is available
>>
>> Enrico
>>
>>
>> Il giorno mer 7 ott 2020 alle ore 11:01 Damien Diederen <
>> ddiederen@sinenomine.net> ha scritto:
>>
>> >
>> > Hello, everybody.
>> >
>> > Would you have any feedback on this?
>> >
>> > Cheers, -D
>> >
>> >
>> >
>> > Damien Diederen <dd...@sinenomine.net> writes:
>> > > Greetings, all,
>> > >
>> > > I haven't initially tried to get the C SASL patches integrated in the
>> > > 3.6 branch, as they were not very mature and as I had noticed the
>> > > increased release cadence in the project.
>> > >
>> > > But I am now wondering: do we already have a time horizon for ZooKeeper
>> > > 3.7? Or are we waiting for a sufficient number of features to
>> > > "accumulate" in master?
>> > >
>> > > (I understand that each branch causes additional overhead, and that we
>> > > may not want to have a long ladder of cherry-picks for each patch
>> coming
>> > > in.)
>> > >
>> > > In case there aren't any short-term plans, I would like to backport the
>> > > C and Perl SASL patches to 3.6, as they've now matured a fair bit and
>> as
>> > > those patches shouldn't impact the rest of the system.
>> > >
>> > > What do you think?
>> > >
>> > > Cheers, -D
>> >
>>
Re: ZooKeeper 3.7 timeline? C SASL backport?
Posted by Tamas Penzes <ta...@cloudera.com.INVALID>.
Hi All,
Let me add my two cents.
As I have done some cleanups and version updates recently I'd like to get
the following changes in 3.7:
- ZOOKEEPER-3956
- ZOOKEEPER-3958
These are the ones already waiting for review/commit and I think they would
worth to get in before someone cuts a release.
Thanks, Tamaas
On Wed, Oct 7, 2020 at 12:04 PM Enrico Olivelli <eo...@gmail.com> wrote:
> Sorry Damien,
> I thought I had answered to you but my message was never sent :-(
>
> I think that master branch is in very good shape and we had feedback from
> users about 3.6.x, in fact we already released 3.6.1 and 3.6.2.
>
> Cutting 3.7.0 will also be a sign that the current "stable" version is
> 3.6., and this is very good.
>
> Let's see if any committer volunteers to cut the release.
> I will have time by the end of the month if no one else is available
>
> Enrico
>
>
> Il giorno mer 7 ott 2020 alle ore 11:01 Damien Diederen <
> ddiederen@sinenomine.net> ha scritto:
>
> >
> > Hello, everybody.
> >
> > Would you have any feedback on this?
> >
> > Cheers, -D
> >
> >
> >
> > Damien Diederen <dd...@sinenomine.net> writes:
> > > Greetings, all,
> > >
> > > I haven't initially tried to get the C SASL patches integrated in the
> > > 3.6 branch, as they were not very mature and as I had noticed the
> > > increased release cadence in the project.
> > >
> > > But I am now wondering: do we already have a time horizon for ZooKeeper
> > > 3.7? Or are we waiting for a sufficient number of features to
> > > "accumulate" in master?
> > >
> > > (I understand that each branch causes additional overhead, and that we
> > > may not want to have a long ladder of cherry-picks for each patch
> coming
> > > in.)
> > >
> > > In case there aren't any short-term plans, I would like to backport the
> > > C and Perl SASL patches to 3.6, as they've now matured a fair bit and
> as
> > > those patches shouldn't impact the rest of the system.
> > >
> > > What do you think?
> > >
> > > Cheers, -D
> >
>