You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by Kezhu Wang <ke...@apache.org> on 2023/04/06 07:35:47 UTC

[DISCUSS] Cutting a release ? 5.5.0 ?

The last release 5.4.0 was released on 2022.11.03, it was five month ago.
And we have accumulated at least 8 fixes, some of them are long-time
issues. I think it might be time to prepare the next release for them.

There are currently two version tags 5.4.1[1] and 5.5.0[2] at jira. I
prefer 5.5.0 since at least two issues touched the `public` part:
* CURATOR-535[3] and its pr#421[4] made the `ZooKeeperMainFace` package
private.
* CURATOR-662[5] and its pr#448[6] exported `getLockPath` from `protected`
to `public`.

Besides the version tag, there are ongoing issues:
* CURATOR-666[7] is about to conclude. I prefer to include it in the next
release.
* CURATOR-609[8] has been dangling for years and its author pinged a week
ago. I think it might be worth taking a look at it and concluding a version
for it.

Any thoughts ? I will take a look for CURATOR-609 anyway.

[1]: https://issues.apache.org/jira/projects/CURATOR/versions/12352446
[2]: https://issues.apache.org/jira/projects/CURATOR/versions/12352495
[3]: https://issues.apache.org/jira/browse/CURATOR-535
[4]: https://github.com/apache/curator/pull/421
[5]: https://issues.apache.org/jira/browse/CURATOR-662
[6]: https://github.com/apache/curator/pull/448
[7]: https://issues.apache.org/jira/browse/CURATOR-666
[8]: https://issues.apache.org/jira/browse/CURATOR-609

-- 
Best,
Kezhu Wang

Re: [DISCUSS] Cutting a release ? 5.5.0 ?

Posted by Kezhu Wang <ke...@gmail.com>.

Hi Jordan,

I think we can conclude VOTE after that day, hopefully we can release it
before May 1.

I don't think we are in a hurry on anything.

Thank you for your support.

Best,
Kezhu Wang


On Fri, Apr 14, 2023 at 12:19 PM Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:

> I'll be on vacation until April 24 - FYI
>
> > On Apr 14, 2023, at 4:42 AM, Kezhu Wang <ke...@apache.org> wrote:
> >
> > Hi all,
> >
> > Thank you for your support. I plan to cut the release next Wednesday
> > (2023-04-19). If there are no more comments about CURATOR-666[1][2], I
> also
> > plan to merge it before releasing.
> >
> > Please let me know your concerns before that day.
> >
> > [1]: https://issues.apache.org/jira/browse/CURATOR-666
> > [2]: https://github.com/apache/curator/pull/454
> >
> > Best,
> > Kezhu Wang
> >
> >
> > On Fri, Apr 7, 2023 at 6:37 PM tison <wa...@gmail.com> wrote:
> >
> >> If Jordan or Enrico can look at CURATOR-666 and its PR, we may include
> it
> >> in this release. The implementation and rationale should be relatively
> >> simple to review.
> >>
> >> Best,
> >> tison.
> >>
> >>
> >> tison <wa...@gmail.com> 于2023年4月7日周五 18:34写道：
> >>
> >>> I agree that the next release can be 5.5.0.
> >>>
> >>> Looking forward to the next steps :)
> >>>
> >>> Best,
> >>> tison.
> >>>
> >>>
> >>> Jordan Zimmerman <jo...@jordanzimmerman.com> 于2023年4月6日周四 17:15写道：
> >>>
> >>>> OK with me
> >>>>
> >>>>> On Apr 6, 2023, at 8:35 AM, Kezhu Wang <ke...@apache.org> wrote:
> >>>>>
> >>>>> The last release 5.4.0 was released on 2022.11.03, it was five month
> >>>> ago.
> >>>>> And we have accumulated at least 8 fixes, some of them are long-time
> >>>>> issues. I think it might be time to prepare the next release for
> them.
> >>>>>
> >>>>> There are currently two version tags 5.4.1[1] and 5.5.0[2] at jira. I
> >>>>> prefer 5.5.0 since at least two issues touched the `public` part:
> >>>>> * CURATOR-535[3] and its pr#421[4] made the `ZooKeeperMainFace`
> >> package
> >>>>> private.
> >>>>> * CURATOR-662[5] and its pr#448[6] exported `getLockPath` from
> >>>> `protected`
> >>>>> to `public`.
> >>>>>
> >>>>> Besides the version tag, there are ongoing issues:
> >>>>> * CURATOR-666[7] is about to conclude. I prefer to include it in the
> >>>> next
> >>>>> release.
> >>>>> * CURATOR-609[8] has been dangling for years and its author pinged a
> >>>> week
> >>>>> ago. I think it might be worth taking a look at it and concluding a
> >>>> version
> >>>>> for it.
> >>>>>
> >>>>> Any thoughts ? I will take a look for CURATOR-609 anyway.
> >>>>>
> >>>>> [1]:
> >> https://issues.apache.org/jira/projects/CURATOR/versions/12352446
> >>>>> [2]:
> >> https://issues.apache.org/jira/projects/CURATOR/versions/12352495
> >>>>> [3]: https://issues.apache.org/jira/browse/CURATOR-535
> >>>>> [4]: https://github.com/apache/curator/pull/421
> >>>>> [5]: https://issues.apache.org/jira/browse/CURATOR-662
> >>>>> [6]: https://github.com/apache/curator/pull/448
> >>>>> [7]: https://issues.apache.org/jira/browse/CURATOR-666
> >>>>> [8]: https://issues.apache.org/jira/browse/CURATOR-609
> >>>>>
> >>>>> --
> >>>>> Best,
> >>>>> Kezhu Wang
> >>>>
> >>>>
> >>
>
>

Re: [DISCUSS] Cutting a release ? 5.5.0 ?

Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.

I'll be on vacation until April 24 - FYI

> On Apr 14, 2023, at 4:42 AM, Kezhu Wang <ke...@apache.org> wrote:
> 
> Hi all,
> 
> Thank you for your support. I plan to cut the release next Wednesday
> (2023-04-19). If there are no more comments about CURATOR-666[1][2], I also
> plan to merge it before releasing.
> 
> Please let me know your concerns before that day.
> 
> [1]: https://issues.apache.org/jira/browse/CURATOR-666
> [2]: https://github.com/apache/curator/pull/454
> 
> Best,
> Kezhu Wang
> 
> 
> On Fri, Apr 7, 2023 at 6:37 PM tison <wa...@gmail.com> wrote:
> 
>> If Jordan or Enrico can look at CURATOR-666 and its PR, we may include it
>> in this release. The implementation and rationale should be relatively
>> simple to review.
>> 
>> Best,
>> tison.
>> 
>> 
>> tison <wa...@gmail.com> 于2023年4月7日周五 18:34写道：
>> 
>>> I agree that the next release can be 5.5.0.
>>> 
>>> Looking forward to the next steps :)
>>> 
>>> Best,
>>> tison.
>>> 
>>> 
>>> Jordan Zimmerman <jo...@jordanzimmerman.com> 于2023年4月6日周四 17:15写道：
>>> 
>>>> OK with me
>>>> 
>>>>> On Apr 6, 2023, at 8:35 AM, Kezhu Wang <ke...@apache.org> wrote:
>>>>> 
>>>>> The last release 5.4.0 was released on 2022.11.03, it was five month
>>>> ago.
>>>>> And we have accumulated at least 8 fixes, some of them are long-time
>>>>> issues. I think it might be time to prepare the next release for them.
>>>>> 
>>>>> There are currently two version tags 5.4.1[1] and 5.5.0[2] at jira. I
>>>>> prefer 5.5.0 since at least two issues touched the `public` part:
>>>>> * CURATOR-535[3] and its pr#421[4] made the `ZooKeeperMainFace`
>> package
>>>>> private.
>>>>> * CURATOR-662[5] and its pr#448[6] exported `getLockPath` from
>>>> `protected`
>>>>> to `public`.
>>>>> 
>>>>> Besides the version tag, there are ongoing issues:
>>>>> * CURATOR-666[7] is about to conclude. I prefer to include it in the
>>>> next
>>>>> release.
>>>>> * CURATOR-609[8] has been dangling for years and its author pinged a
>>>> week
>>>>> ago. I think it might be worth taking a look at it and concluding a
>>>> version
>>>>> for it.
>>>>> 
>>>>> Any thoughts ? I will take a look for CURATOR-609 anyway.
>>>>> 
>>>>> [1]:
>> https://issues.apache.org/jira/projects/CURATOR/versions/12352446
>>>>> [2]:
>> https://issues.apache.org/jira/projects/CURATOR/versions/12352495
>>>>> [3]: https://issues.apache.org/jira/browse/CURATOR-535
>>>>> [4]: https://github.com/apache/curator/pull/421
>>>>> [5]: https://issues.apache.org/jira/browse/CURATOR-662
>>>>> [6]: https://github.com/apache/curator/pull/448
>>>>> [7]: https://issues.apache.org/jira/browse/CURATOR-666
>>>>> [8]: https://issues.apache.org/jira/browse/CURATOR-609
>>>>> 
>>>>> --
>>>>> Best,
>>>>> Kezhu Wang
>>>> 
>>>> 
>>

Re: [DISCUSS] Cutting a release ? 5.5.0 ?

Posted by Kezhu Wang <ke...@apache.org>.

Hi all,

Thank you for your support. I plan to cut the release next Wednesday
(2023-04-19). If there are no more comments about CURATOR-666[1][2], I also
plan to merge it before releasing.

Please let me know your concerns before that day.

[1]: https://issues.apache.org/jira/browse/CURATOR-666
[2]: https://github.com/apache/curator/pull/454

Best,
Kezhu Wang


On Fri, Apr 7, 2023 at 6:37 PM tison <wa...@gmail.com> wrote:

> If Jordan or Enrico can look at CURATOR-666 and its PR, we may include it
> in this release. The implementation and rationale should be relatively
> simple to review.
>
> Best,
> tison.
>
>
> tison <wa...@gmail.com> 于2023年4月7日周五 18:34写道：
>
> > I agree that the next release can be 5.5.0.
> >
> > Looking forward to the next steps :)
> >
> > Best,
> > tison.
> >
> >
> > Jordan Zimmerman <jo...@jordanzimmerman.com> 于2023年4月6日周四 17:15写道：
> >
> >> OK with me
> >>
> >> > On Apr 6, 2023, at 8:35 AM, Kezhu Wang <ke...@apache.org> wrote:
> >> >
> >> > The last release 5.4.0 was released on 2022.11.03, it was five month
> >> ago.
> >> > And we have accumulated at least 8 fixes, some of them are long-time
> >> > issues. I think it might be time to prepare the next release for them.
> >> >
> >> > There are currently two version tags 5.4.1[1] and 5.5.0[2] at jira. I
> >> > prefer 5.5.0 since at least two issues touched the `public` part:
> >> > * CURATOR-535[3] and its pr#421[4] made the `ZooKeeperMainFace`
> package
> >> > private.
> >> > * CURATOR-662[5] and its pr#448[6] exported `getLockPath` from
> >> `protected`
> >> > to `public`.
> >> >
> >> > Besides the version tag, there are ongoing issues:
> >> > * CURATOR-666[7] is about to conclude. I prefer to include it in the
> >> next
> >> > release.
> >> > * CURATOR-609[8] has been dangling for years and its author pinged a
> >> week
> >> > ago. I think it might be worth taking a look at it and concluding a
> >> version
> >> > for it.
> >> >
> >> > Any thoughts ? I will take a look for CURATOR-609 anyway.
> >> >
> >> > [1]:
> https://issues.apache.org/jira/projects/CURATOR/versions/12352446
> >> > [2]:
> https://issues.apache.org/jira/projects/CURATOR/versions/12352495
> >> > [3]: https://issues.apache.org/jira/browse/CURATOR-535
> >> > [4]: https://github.com/apache/curator/pull/421
> >> > [5]: https://issues.apache.org/jira/browse/CURATOR-662
> >> > [6]: https://github.com/apache/curator/pull/448
> >> > [7]: https://issues.apache.org/jira/browse/CURATOR-666
> >> > [8]: https://issues.apache.org/jira/browse/CURATOR-609
> >> >
> >> > --
> >> > Best,
> >> > Kezhu Wang
> >>
> >>
>

Re: [DISCUSS] Cutting a release ? 5.5.0 ?

Posted by tison <wa...@gmail.com>.

If Jordan or Enrico can look at CURATOR-666 and its PR, we may include it
in this release. The implementation and rationale should be relatively
simple to review.

Best,
tison.


tison <wa...@gmail.com> 于2023年4月7日周五 18:34写道：

> I agree that the next release can be 5.5.0.
>
> Looking forward to the next steps :)
>
> Best,
> tison.
>
>
> Jordan Zimmerman <jo...@jordanzimmerman.com> 于2023年4月6日周四 17:15写道：
>
>> OK with me
>>
>> > On Apr 6, 2023, at 8:35 AM, Kezhu Wang <ke...@apache.org> wrote:
>> >
>> > The last release 5.4.0 was released on 2022.11.03, it was five month
>> ago.
>> > And we have accumulated at least 8 fixes, some of them are long-time
>> > issues. I think it might be time to prepare the next release for them.
>> >
>> > There are currently two version tags 5.4.1[1] and 5.5.0[2] at jira. I
>> > prefer 5.5.0 since at least two issues touched the `public` part:
>> > * CURATOR-535[3] and its pr#421[4] made the `ZooKeeperMainFace` package
>> > private.
>> > * CURATOR-662[5] and its pr#448[6] exported `getLockPath` from
>> `protected`
>> > to `public`.
>> >
>> > Besides the version tag, there are ongoing issues:
>> > * CURATOR-666[7] is about to conclude. I prefer to include it in the
>> next
>> > release.
>> > * CURATOR-609[8] has been dangling for years and its author pinged a
>> week
>> > ago. I think it might be worth taking a look at it and concluding a
>> version
>> > for it.
>> >
>> > Any thoughts ? I will take a look for CURATOR-609 anyway.
>> >
>> > [1]: https://issues.apache.org/jira/projects/CURATOR/versions/12352446
>> > [2]: https://issues.apache.org/jira/projects/CURATOR/versions/12352495
>> > [3]: https://issues.apache.org/jira/browse/CURATOR-535
>> > [4]: https://github.com/apache/curator/pull/421
>> > [5]: https://issues.apache.org/jira/browse/CURATOR-662
>> > [6]: https://github.com/apache/curator/pull/448
>> > [7]: https://issues.apache.org/jira/browse/CURATOR-666
>> > [8]: https://issues.apache.org/jira/browse/CURATOR-609
>> >
>> > --
>> > Best,
>> > Kezhu Wang
>>
>>

Re: [DISCUSS] Cutting a release ? 5.5.0 ?

Posted by tison <wa...@gmail.com>.

I agree that the next release can be 5.5.0.

Looking forward to the next steps :)

Best,
tison.


Jordan Zimmerman <jo...@jordanzimmerman.com> 于2023年4月6日周四 17:15写道：

> OK with me
>
> > On Apr 6, 2023, at 8:35 AM, Kezhu Wang <ke...@apache.org> wrote:
> >
> > The last release 5.4.0 was released on 2022.11.03, it was five month ago.
> > And we have accumulated at least 8 fixes, some of them are long-time
> > issues. I think it might be time to prepare the next release for them.
> >
> > There are currently two version tags 5.4.1[1] and 5.5.0[2] at jira. I
> > prefer 5.5.0 since at least two issues touched the `public` part:
> > * CURATOR-535[3] and its pr#421[4] made the `ZooKeeperMainFace` package
> > private.
> > * CURATOR-662[5] and its pr#448[6] exported `getLockPath` from
> `protected`
> > to `public`.
> >
> > Besides the version tag, there are ongoing issues:
> > * CURATOR-666[7] is about to conclude. I prefer to include it in the next
> > release.
> > * CURATOR-609[8] has been dangling for years and its author pinged a week
> > ago. I think it might be worth taking a look at it and concluding a
> version
> > for it.
> >
> > Any thoughts ? I will take a look for CURATOR-609 anyway.
> >
> > [1]: https://issues.apache.org/jira/projects/CURATOR/versions/12352446
> > [2]: https://issues.apache.org/jira/projects/CURATOR/versions/12352495
> > [3]: https://issues.apache.org/jira/browse/CURATOR-535
> > [4]: https://github.com/apache/curator/pull/421
> > [5]: https://issues.apache.org/jira/browse/CURATOR-662
> > [6]: https://github.com/apache/curator/pull/448
> > [7]: https://issues.apache.org/jira/browse/CURATOR-666
> > [8]: https://issues.apache.org/jira/browse/CURATOR-609
> >
> > --
> > Best,
> > Kezhu Wang
>
>

Re: [DISCUSS] Cutting a release ? 5.5.0 ?

Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.

OK with me

> On Apr 6, 2023, at 8:35 AM, Kezhu Wang <ke...@apache.org> wrote:
> 
> The last release 5.4.0 was released on 2022.11.03, it was five month ago.
> And we have accumulated at least 8 fixes, some of them are long-time
> issues. I think it might be time to prepare the next release for them.
> 
> There are currently two version tags 5.4.1[1] and 5.5.0[2] at jira. I
> prefer 5.5.0 since at least two issues touched the `public` part:
> * CURATOR-535[3] and its pr#421[4] made the `ZooKeeperMainFace` package
> private.
> * CURATOR-662[5] and its pr#448[6] exported `getLockPath` from `protected`
> to `public`.
> 
> Besides the version tag, there are ongoing issues:
> * CURATOR-666[7] is about to conclude. I prefer to include it in the next
> release.
> * CURATOR-609[8] has been dangling for years and its author pinged a week
> ago. I think it might be worth taking a look at it and concluding a version
> for it.
> 
> Any thoughts ? I will take a look for CURATOR-609 anyway.
> 
> [1]: https://issues.apache.org/jira/projects/CURATOR/versions/12352446
> [2]: https://issues.apache.org/jira/projects/CURATOR/versions/12352495
> [3]: https://issues.apache.org/jira/browse/CURATOR-535
> [4]: https://github.com/apache/curator/pull/421
> [5]: https://issues.apache.org/jira/browse/CURATOR-662
> [6]: https://github.com/apache/curator/pull/448
> [7]: https://issues.apache.org/jira/browse/CURATOR-666
> [8]: https://issues.apache.org/jira/browse/CURATOR-609
> 
> -- 
> Best,
> Kezhu Wang