You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Christophe Bornet <bo...@gmail.com> on 2023/01/19 23:11:09 UTC
[DISCUSS] Code freeze for Pulsar 2.12
Hi Pulsar community,
It's great that we released Pulsar 2.11. It has taken quite some time to
stabilize the release branch and now we have more than 5 months of awesome
features and commits on the master branch that would benefit a lot to our
users. That's why I'd like to propose to start a code freeze for the
release of Pulsar 2.12 with a target release date by mid/end-february.
Hopefully this release will be easier to stabilize but we don't know for
sure, so better to start the release activities asap.
We also need a release manager. Nicolo proposed himself last time but had
to hand over because of his holiday schedule. So Nicolo, maybe you'd like
to propose yourself again for this one ? Otherwise I'm happy to volunteer.
Let me know what you think.
Cheers
Christophe
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Enrico Olivelli <eo...@gmail.com>.
Il giorno gio 2 feb 2023 alle ore 08:08 Haiting Jiang
<ji...@gmail.com> ha scritto:
>
> > Following PIP-175, we have to provide the first LTS release which will be 3.0.
>
> Actuall as discussed in [1], the first LTS release is 2.10 for being
> the last Java 8 release.
> The major version 3.0 bump would simply signal the type of the release.
>
> I think we should make a VOTE on PIP-175 officially.
I agree
Enrico
>
> [1] https://lists.apache.org/thread/4pj3f9zjb6hm1cnvvnqzm1v2cl588wxp
>
> Thanks,
> Haiting
>
> On Fri, Jan 20, 2023 at 7:07 PM Nicolò Boschi <bo...@gmail.com> wrote:
> >
> > From my understanding we should follow PIP-175.
> > Actually it has not been officially voted on but we can address that easily.
> >
> > Following PIP-175, we have to provide the first LTS release which will be
> > 3.0.
> > The code freeze should happen 3 weeks before the target date.
> > If we target 3 months from now to have 3.0 released, let's say mid April,
> > we should consider the time for:
> > 1. bureaucracy of the release - ~1 week
> > 2. the vote ~ 2 weeks
> > 3. the code freeze ~ 3 weeks
> >
> > So the code freeze should start 6 weeks before the target date, in this
> > case at the beginning of March.
> > Code freeze is intended as (from PIP-175):
> > "The release manager will branch off from master, and he will be
> > responsible for selecting the changes that will be cherry-picked in the
> > release branch."
> >
> > So we need to have a release manager that at the beginning of March:
> > - creates the 3.0 branch
> > - must approve every cherry-pick (the best would be to require to open pull
> > requests against the branch 3.0 and have the release manager as submitter
> > or reviewer)
> > - call the vote on the third week of March
> >
> >
> > This plan makes sense to me.
> > The estimate for the above steps are debatable and should be part of
> > PIP-175.
> >
> > Since, as Christophe said, we have tons of new stuff (since August) in the
> > master branch we might take a different target date but it also depends on
> > the features that are not fully completed but already partially committed
> > on the master branch).
> > Also this is a new process, it's okay to have some delays for the first LTS
> > release.
> >
> > I'd be happy to guide the 3.0 release
> >
> > Nicolò Boschi
> >
> >
> > Il giorno ven 20 gen 2023 alle ore 11:46 Christophe Bornet <
> > bornet.chris@gmail.com> ha scritto:
> >
> > > We could create the release branch some days after the Chinese holidays.
> > > The idea is to not wait too long before starting the release activities.
> > > Especially since 2.11 has taken so long to release.
> > >
> > > Le ven. 20 janv. 2023 à 03:41, Dave Fisher <wa...@comcast.net> a
> > > écrit :
> > >
> > > > Christophe,
> > > >
> > > > Given the Chinese New Year what freeze date is being proposed?
> > > >
> > > > Best,
> > > > Dave
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On Jan 19, 2023, at 6:31 PM, Yunze Xu <yz...@streamnative.io.invalid>
> > > > wrote:
> > > > >
> > > > > In addition, next week is the Chinese New Year [1] in China and there
> > > > > is a long holiday (a week) for Chinese developers. I hope we can delay
> > > > > this release for a while.
> > > > >
> > > > > [1] https://en.wikipedia.org/wiki/Chinese_New_Year
> > > > >
> > > > > Thanks,
> > > > > Yunze
> > > > >
> > > > >> On Fri, Jan 20, 2023 at 10:23 AM Yunze Xu <yz...@streamnative.io>
> > > wrote:
> > > > >>
> > > > >> I would like to include PIP-224 (even and PIP-229) in the next major
> > > > >> releases. These two PIPs have some impacts on the API and could bring
> > > > >> many benefits to ecosystem developers. But unfortunately the first PR
> > > > >> of PIP-224 [1] is still not reviewed by anyone. The code has already
> > > > >> been added locally and only requires some rebase to resolve conflicts.
> > > > >>
> > > > >> [1] https://github.com/apache/pulsar/pull/19158
> > > > >>
> > > > >> Thanks,
> > > > >> Yunze
> > > > >>
> > > > >>> On Fri, Jan 20, 2023 at 7:46 AM <ma...@gmail.com> wrote:
> > > > >>>
> > > > >>> Isn't the next version LTS 3.0?
> > > > >>>
> > > > >>> Best
> > > > >>> Mattison
> > > > >>> On Jan 20, 2023, 07:11 +0800, Christophe Bornet <
> > > > bornet.chris@gmail.com>, wrote:
> > > > >>>> Hi Pulsar community,
> > > > >>>>
> > > > >>>> It's great that we released Pulsar 2.11. It has taken quite some
> > > time
> > > > to
> > > > >>>> stabilize the release branch and now we have more than 5 months of
> > > > awesome
> > > > >>>> features and commits on the master branch that would benefit a lot
> > > to
> > > > our
> > > > >>>> users. That's why I'd like to propose to start a code freeze for the
> > > > >>>> release of Pulsar 2.12 with a target release date by
> > > mid/end-february.
> > > > >>>> Hopefully this release will be easier to stabilize but we don't know
> > > > for
> > > > >>>> sure, so better to start the release activities asap.
> > > > >>>> We also need a release manager. Nicolo proposed himself last time
> > > but
> > > > had
> > > > >>>> to hand over because of his holiday schedule. So Nicolo, maybe you'd
> > > > like
> > > > >>>> to propose yourself again for this one ? Otherwise I'm happy to
> > > > volunteer.
> > > > >>>>
> > > > >>>> Let me know what you think.
> > > > >>>>
> > > > >>>> Cheers
> > > > >>>>
> > > > >>>> Christophe
> > > >
> > >
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Haiting Jiang <ji...@gmail.com>.
> Following PIP-175, we have to provide the first LTS release which will be 3.0.
Actuall as discussed in [1], the first LTS release is 2.10 for being
the last Java 8 release.
The major version 3.0 bump would simply signal the type of the release.
I think we should make a VOTE on PIP-175 officially.
[1] https://lists.apache.org/thread/4pj3f9zjb6hm1cnvvnqzm1v2cl588wxp
Thanks,
Haiting
On Fri, Jan 20, 2023 at 7:07 PM Nicolò Boschi <bo...@gmail.com> wrote:
>
> From my understanding we should follow PIP-175.
> Actually it has not been officially voted on but we can address that easily.
>
> Following PIP-175, we have to provide the first LTS release which will be
> 3.0.
> The code freeze should happen 3 weeks before the target date.
> If we target 3 months from now to have 3.0 released, let's say mid April,
> we should consider the time for:
> 1. bureaucracy of the release - ~1 week
> 2. the vote ~ 2 weeks
> 3. the code freeze ~ 3 weeks
>
> So the code freeze should start 6 weeks before the target date, in this
> case at the beginning of March.
> Code freeze is intended as (from PIP-175):
> "The release manager will branch off from master, and he will be
> responsible for selecting the changes that will be cherry-picked in the
> release branch."
>
> So we need to have a release manager that at the beginning of March:
> - creates the 3.0 branch
> - must approve every cherry-pick (the best would be to require to open pull
> requests against the branch 3.0 and have the release manager as submitter
> or reviewer)
> - call the vote on the third week of March
>
>
> This plan makes sense to me.
> The estimate for the above steps are debatable and should be part of
> PIP-175.
>
> Since, as Christophe said, we have tons of new stuff (since August) in the
> master branch we might take a different target date but it also depends on
> the features that are not fully completed but already partially committed
> on the master branch).
> Also this is a new process, it's okay to have some delays for the first LTS
> release.
>
> I'd be happy to guide the 3.0 release
>
> Nicolò Boschi
>
>
> Il giorno ven 20 gen 2023 alle ore 11:46 Christophe Bornet <
> bornet.chris@gmail.com> ha scritto:
>
> > We could create the release branch some days after the Chinese holidays.
> > The idea is to not wait too long before starting the release activities.
> > Especially since 2.11 has taken so long to release.
> >
> > Le ven. 20 janv. 2023 à 03:41, Dave Fisher <wa...@comcast.net> a
> > écrit :
> >
> > > Christophe,
> > >
> > > Given the Chinese New Year what freeze date is being proposed?
> > >
> > > Best,
> > > Dave
> > >
> > > Sent from my iPhone
> > >
> > > > On Jan 19, 2023, at 6:31 PM, Yunze Xu <yz...@streamnative.io.invalid>
> > > wrote:
> > > >
> > > > In addition, next week is the Chinese New Year [1] in China and there
> > > > is a long holiday (a week) for Chinese developers. I hope we can delay
> > > > this release for a while.
> > > >
> > > > [1] https://en.wikipedia.org/wiki/Chinese_New_Year
> > > >
> > > > Thanks,
> > > > Yunze
> > > >
> > > >> On Fri, Jan 20, 2023 at 10:23 AM Yunze Xu <yz...@streamnative.io>
> > wrote:
> > > >>
> > > >> I would like to include PIP-224 (even and PIP-229) in the next major
> > > >> releases. These two PIPs have some impacts on the API and could bring
> > > >> many benefits to ecosystem developers. But unfortunately the first PR
> > > >> of PIP-224 [1] is still not reviewed by anyone. The code has already
> > > >> been added locally and only requires some rebase to resolve conflicts.
> > > >>
> > > >> [1] https://github.com/apache/pulsar/pull/19158
> > > >>
> > > >> Thanks,
> > > >> Yunze
> > > >>
> > > >>> On Fri, Jan 20, 2023 at 7:46 AM <ma...@gmail.com> wrote:
> > > >>>
> > > >>> Isn't the next version LTS 3.0?
> > > >>>
> > > >>> Best
> > > >>> Mattison
> > > >>> On Jan 20, 2023, 07:11 +0800, Christophe Bornet <
> > > bornet.chris@gmail.com>, wrote:
> > > >>>> Hi Pulsar community,
> > > >>>>
> > > >>>> It's great that we released Pulsar 2.11. It has taken quite some
> > time
> > > to
> > > >>>> stabilize the release branch and now we have more than 5 months of
> > > awesome
> > > >>>> features and commits on the master branch that would benefit a lot
> > to
> > > our
> > > >>>> users. That's why I'd like to propose to start a code freeze for the
> > > >>>> release of Pulsar 2.12 with a target release date by
> > mid/end-february.
> > > >>>> Hopefully this release will be easier to stabilize but we don't know
> > > for
> > > >>>> sure, so better to start the release activities asap.
> > > >>>> We also need a release manager. Nicolo proposed himself last time
> > but
> > > had
> > > >>>> to hand over because of his holiday schedule. So Nicolo, maybe you'd
> > > like
> > > >>>> to propose yourself again for this one ? Otherwise I'm happy to
> > > volunteer.
> > > >>>>
> > > >>>> Let me know what you think.
> > > >>>>
> > > >>>> Cheers
> > > >>>>
> > > >>>> Christophe
> > >
> >
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by PengHui Li <pe...@apache.org>.
I have updated the milestone name from 2.12.0 to 3.0.0.
https://github.com/apache/pulsar/milestone/34
Penghui
On Fri, Jan 20, 2023 at 7:07 PM Nicolò Boschi <bo...@gmail.com> wrote:
> From my understanding we should follow PIP-175.
> Actually it has not been officially voted on but we can address that
> easily.
>
> Following PIP-175, we have to provide the first LTS release which will be
> 3.0.
> The code freeze should happen 3 weeks before the target date.
> If we target 3 months from now to have 3.0 released, let's say mid April,
> we should consider the time for:
> 1. bureaucracy of the release - ~1 week
> 2. the vote ~ 2 weeks
> 3. the code freeze ~ 3 weeks
>
> So the code freeze should start 6 weeks before the target date, in this
> case at the beginning of March.
> Code freeze is intended as (from PIP-175):
> "The release manager will branch off from master, and he will be
> responsible for selecting the changes that will be cherry-picked in the
> release branch."
>
> So we need to have a release manager that at the beginning of March:
> - creates the 3.0 branch
> - must approve every cherry-pick (the best would be to require to open pull
> requests against the branch 3.0 and have the release manager as submitter
> or reviewer)
> - call the vote on the third week of March
>
>
> This plan makes sense to me.
> The estimate for the above steps are debatable and should be part of
> PIP-175.
>
> Since, as Christophe said, we have tons of new stuff (since August) in the
> master branch we might take a different target date but it also depends on
> the features that are not fully completed but already partially committed
> on the master branch).
> Also this is a new process, it's okay to have some delays for the first LTS
> release.
>
> I'd be happy to guide the 3.0 release
>
> Nicolò Boschi
>
>
> Il giorno ven 20 gen 2023 alle ore 11:46 Christophe Bornet <
> bornet.chris@gmail.com> ha scritto:
>
> > We could create the release branch some days after the Chinese holidays.
> > The idea is to not wait too long before starting the release activities.
> > Especially since 2.11 has taken so long to release.
> >
> > Le ven. 20 janv. 2023 à 03:41, Dave Fisher <wa...@comcast.net> a
> > écrit :
> >
> > > Christophe,
> > >
> > > Given the Chinese New Year what freeze date is being proposed?
> > >
> > > Best,
> > > Dave
> > >
> > > Sent from my iPhone
> > >
> > > > On Jan 19, 2023, at 6:31 PM, Yunze Xu <yz...@streamnative.io.invalid>
> > > wrote:
> > > >
> > > > In addition, next week is the Chinese New Year [1] in China and
> there
> > > > is a long holiday (a week) for Chinese developers. I hope we can
> delay
> > > > this release for a while.
> > > >
> > > > [1] https://en.wikipedia.org/wiki/Chinese_New_Year
> > > >
> > > > Thanks,
> > > > Yunze
> > > >
> > > >> On Fri, Jan 20, 2023 at 10:23 AM Yunze Xu <yz...@streamnative.io>
> > wrote:
> > > >>
> > > >> I would like to include PIP-224 (even and PIP-229) in the next major
> > > >> releases. These two PIPs have some impacts on the API and could
> bring
> > > >> many benefits to ecosystem developers. But unfortunately the first
> PR
> > > >> of PIP-224 [1] is still not reviewed by anyone. The code has already
> > > >> been added locally and only requires some rebase to resolve
> conflicts.
> > > >>
> > > >> [1] https://github.com/apache/pulsar/pull/19158
> > > >>
> > > >> Thanks,
> > > >> Yunze
> > > >>
> > > >>> On Fri, Jan 20, 2023 at 7:46 AM <ma...@gmail.com> wrote:
> > > >>>
> > > >>> Isn't the next version LTS 3.0?
> > > >>>
> > > >>> Best
> > > >>> Mattison
> > > >>> On Jan 20, 2023, 07:11 +0800, Christophe Bornet <
> > > bornet.chris@gmail.com>, wrote:
> > > >>>> Hi Pulsar community,
> > > >>>>
> > > >>>> It's great that we released Pulsar 2.11. It has taken quite some
> > time
> > > to
> > > >>>> stabilize the release branch and now we have more than 5 months of
> > > awesome
> > > >>>> features and commits on the master branch that would benefit a lot
> > to
> > > our
> > > >>>> users. That's why I'd like to propose to start a code freeze for
> the
> > > >>>> release of Pulsar 2.12 with a target release date by
> > mid/end-february.
> > > >>>> Hopefully this release will be easier to stabilize but we don't
> know
> > > for
> > > >>>> sure, so better to start the release activities asap.
> > > >>>> We also need a release manager. Nicolo proposed himself last time
> > but
> > > had
> > > >>>> to hand over because of his holiday schedule. So Nicolo, maybe
> you'd
> > > like
> > > >>>> to propose yourself again for this one ? Otherwise I'm happy to
> > > volunteer.
> > > >>>>
> > > >>>> Let me know what you think.
> > > >>>>
> > > >>>> Cheers
> > > >>>>
> > > >>>> Christophe
> > >
> >
>
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Nicolò Boschi <bo...@gmail.com>.
From my understanding we should follow PIP-175.
Actually it has not been officially voted on but we can address that easily.
Following PIP-175, we have to provide the first LTS release which will be
3.0.
The code freeze should happen 3 weeks before the target date.
If we target 3 months from now to have 3.0 released, let's say mid April,
we should consider the time for:
1. bureaucracy of the release - ~1 week
2. the vote ~ 2 weeks
3. the code freeze ~ 3 weeks
So the code freeze should start 6 weeks before the target date, in this
case at the beginning of March.
Code freeze is intended as (from PIP-175):
"The release manager will branch off from master, and he will be
responsible for selecting the changes that will be cherry-picked in the
release branch."
So we need to have a release manager that at the beginning of March:
- creates the 3.0 branch
- must approve every cherry-pick (the best would be to require to open pull
requests against the branch 3.0 and have the release manager as submitter
or reviewer)
- call the vote on the third week of March
This plan makes sense to me.
The estimate for the above steps are debatable and should be part of
PIP-175.
Since, as Christophe said, we have tons of new stuff (since August) in the
master branch we might take a different target date but it also depends on
the features that are not fully completed but already partially committed
on the master branch).
Also this is a new process, it's okay to have some delays for the first LTS
release.
I'd be happy to guide the 3.0 release
Nicolò Boschi
Il giorno ven 20 gen 2023 alle ore 11:46 Christophe Bornet <
bornet.chris@gmail.com> ha scritto:
> We could create the release branch some days after the Chinese holidays.
> The idea is to not wait too long before starting the release activities.
> Especially since 2.11 has taken so long to release.
>
> Le ven. 20 janv. 2023 à 03:41, Dave Fisher <wa...@comcast.net> a
> écrit :
>
> > Christophe,
> >
> > Given the Chinese New Year what freeze date is being proposed?
> >
> > Best,
> > Dave
> >
> > Sent from my iPhone
> >
> > > On Jan 19, 2023, at 6:31 PM, Yunze Xu <yz...@streamnative.io.invalid>
> > wrote:
> > >
> > > In addition, next week is the Chinese New Year [1] in China and there
> > > is a long holiday (a week) for Chinese developers. I hope we can delay
> > > this release for a while.
> > >
> > > [1] https://en.wikipedia.org/wiki/Chinese_New_Year
> > >
> > > Thanks,
> > > Yunze
> > >
> > >> On Fri, Jan 20, 2023 at 10:23 AM Yunze Xu <yz...@streamnative.io>
> wrote:
> > >>
> > >> I would like to include PIP-224 (even and PIP-229) in the next major
> > >> releases. These two PIPs have some impacts on the API and could bring
> > >> many benefits to ecosystem developers. But unfortunately the first PR
> > >> of PIP-224 [1] is still not reviewed by anyone. The code has already
> > >> been added locally and only requires some rebase to resolve conflicts.
> > >>
> > >> [1] https://github.com/apache/pulsar/pull/19158
> > >>
> > >> Thanks,
> > >> Yunze
> > >>
> > >>> On Fri, Jan 20, 2023 at 7:46 AM <ma...@gmail.com> wrote:
> > >>>
> > >>> Isn't the next version LTS 3.0?
> > >>>
> > >>> Best
> > >>> Mattison
> > >>> On Jan 20, 2023, 07:11 +0800, Christophe Bornet <
> > bornet.chris@gmail.com>, wrote:
> > >>>> Hi Pulsar community,
> > >>>>
> > >>>> It's great that we released Pulsar 2.11. It has taken quite some
> time
> > to
> > >>>> stabilize the release branch and now we have more than 5 months of
> > awesome
> > >>>> features and commits on the master branch that would benefit a lot
> to
> > our
> > >>>> users. That's why I'd like to propose to start a code freeze for the
> > >>>> release of Pulsar 2.12 with a target release date by
> mid/end-february.
> > >>>> Hopefully this release will be easier to stabilize but we don't know
> > for
> > >>>> sure, so better to start the release activities asap.
> > >>>> We also need a release manager. Nicolo proposed himself last time
> but
> > had
> > >>>> to hand over because of his holiday schedule. So Nicolo, maybe you'd
> > like
> > >>>> to propose yourself again for this one ? Otherwise I'm happy to
> > volunteer.
> > >>>>
> > >>>> Let me know what you think.
> > >>>>
> > >>>> Cheers
> > >>>>
> > >>>> Christophe
> >
>
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Christophe Bornet <bo...@gmail.com>.
We could create the release branch some days after the Chinese holidays.
The idea is to not wait too long before starting the release activities.
Especially since 2.11 has taken so long to release.
Le ven. 20 janv. 2023 à 03:41, Dave Fisher <wa...@comcast.net> a écrit :
> Christophe,
>
> Given the Chinese New Year what freeze date is being proposed?
>
> Best,
> Dave
>
> Sent from my iPhone
>
> > On Jan 19, 2023, at 6:31 PM, Yunze Xu <yz...@streamnative.io.invalid>
> wrote:
> >
> > In addition, next week is the Chinese New Year [1] in China and there
> > is a long holiday (a week) for Chinese developers. I hope we can delay
> > this release for a while.
> >
> > [1] https://en.wikipedia.org/wiki/Chinese_New_Year
> >
> > Thanks,
> > Yunze
> >
> >> On Fri, Jan 20, 2023 at 10:23 AM Yunze Xu <yz...@streamnative.io> wrote:
> >>
> >> I would like to include PIP-224 (even and PIP-229) in the next major
> >> releases. These two PIPs have some impacts on the API and could bring
> >> many benefits to ecosystem developers. But unfortunately the first PR
> >> of PIP-224 [1] is still not reviewed by anyone. The code has already
> >> been added locally and only requires some rebase to resolve conflicts.
> >>
> >> [1] https://github.com/apache/pulsar/pull/19158
> >>
> >> Thanks,
> >> Yunze
> >>
> >>> On Fri, Jan 20, 2023 at 7:46 AM <ma...@gmail.com> wrote:
> >>>
> >>> Isn't the next version LTS 3.0?
> >>>
> >>> Best
> >>> Mattison
> >>> On Jan 20, 2023, 07:11 +0800, Christophe Bornet <
> bornet.chris@gmail.com>, wrote:
> >>>> Hi Pulsar community,
> >>>>
> >>>> It's great that we released Pulsar 2.11. It has taken quite some time
> to
> >>>> stabilize the release branch and now we have more than 5 months of
> awesome
> >>>> features and commits on the master branch that would benefit a lot to
> our
> >>>> users. That's why I'd like to propose to start a code freeze for the
> >>>> release of Pulsar 2.12 with a target release date by mid/end-february.
> >>>> Hopefully this release will be easier to stabilize but we don't know
> for
> >>>> sure, so better to start the release activities asap.
> >>>> We also need a release manager. Nicolo proposed himself last time but
> had
> >>>> to hand over because of his holiday schedule. So Nicolo, maybe you'd
> like
> >>>> to propose yourself again for this one ? Otherwise I'm happy to
> volunteer.
> >>>>
> >>>> Let me know what you think.
> >>>>
> >>>> Cheers
> >>>>
> >>>> Christophe
>
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Dave Fisher <wa...@comcast.net>.
Christophe,
Given the Chinese New Year what freeze date is being proposed?
Best,
Dave
Sent from my iPhone
> On Jan 19, 2023, at 6:31 PM, Yunze Xu <yz...@streamnative.io.invalid> wrote:
>
> In addition, next week is the Chinese New Year [1] in China and there
> is a long holiday (a week) for Chinese developers. I hope we can delay
> this release for a while.
>
> [1] https://en.wikipedia.org/wiki/Chinese_New_Year
>
> Thanks,
> Yunze
>
>> On Fri, Jan 20, 2023 at 10:23 AM Yunze Xu <yz...@streamnative.io> wrote:
>>
>> I would like to include PIP-224 (even and PIP-229) in the next major
>> releases. These two PIPs have some impacts on the API and could bring
>> many benefits to ecosystem developers. But unfortunately the first PR
>> of PIP-224 [1] is still not reviewed by anyone. The code has already
>> been added locally and only requires some rebase to resolve conflicts.
>>
>> [1] https://github.com/apache/pulsar/pull/19158
>>
>> Thanks,
>> Yunze
>>
>>> On Fri, Jan 20, 2023 at 7:46 AM <ma...@gmail.com> wrote:
>>>
>>> Isn't the next version LTS 3.0?
>>>
>>> Best
>>> Mattison
>>> On Jan 20, 2023, 07:11 +0800, Christophe Bornet <bo...@gmail.com>, wrote:
>>>> Hi Pulsar community,
>>>>
>>>> It's great that we released Pulsar 2.11. It has taken quite some time to
>>>> stabilize the release branch and now we have more than 5 months of awesome
>>>> features and commits on the master branch that would benefit a lot to our
>>>> users. That's why I'd like to propose to start a code freeze for the
>>>> release of Pulsar 2.12 with a target release date by mid/end-february.
>>>> Hopefully this release will be easier to stabilize but we don't know for
>>>> sure, so better to start the release activities asap.
>>>> We also need a release manager. Nicolo proposed himself last time but had
>>>> to hand over because of his holiday schedule. So Nicolo, maybe you'd like
>>>> to propose yourself again for this one ? Otherwise I'm happy to volunteer.
>>>>
>>>> Let me know what you think.
>>>>
>>>> Cheers
>>>>
>>>> Christophe
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Yunze Xu <yz...@streamnative.io.INVALID>.
In addition, next week is the Chinese New Year [1] in China and there
is a long holiday (a week) for Chinese developers. I hope we can delay
this release for a while.
[1] https://en.wikipedia.org/wiki/Chinese_New_Year
Thanks,
Yunze
On Fri, Jan 20, 2023 at 10:23 AM Yunze Xu <yz...@streamnative.io> wrote:
>
> I would like to include PIP-224 (even and PIP-229) in the next major
> releases. These two PIPs have some impacts on the API and could bring
> many benefits to ecosystem developers. But unfortunately the first PR
> of PIP-224 [1] is still not reviewed by anyone. The code has already
> been added locally and only requires some rebase to resolve conflicts.
>
> [1] https://github.com/apache/pulsar/pull/19158
>
> Thanks,
> Yunze
>
> On Fri, Jan 20, 2023 at 7:46 AM <ma...@gmail.com> wrote:
> >
> > Isn't the next version LTS 3.0?
> >
> > Best
> > Mattison
> > On Jan 20, 2023, 07:11 +0800, Christophe Bornet <bo...@gmail.com>, wrote:
> > > Hi Pulsar community,
> > >
> > > It's great that we released Pulsar 2.11. It has taken quite some time to
> > > stabilize the release branch and now we have more than 5 months of awesome
> > > features and commits on the master branch that would benefit a lot to our
> > > users. That's why I'd like to propose to start a code freeze for the
> > > release of Pulsar 2.12 with a target release date by mid/end-february.
> > > Hopefully this release will be easier to stabilize but we don't know for
> > > sure, so better to start the release activities asap.
> > > We also need a release manager. Nicolo proposed himself last time but had
> > > to hand over because of his holiday schedule. So Nicolo, maybe you'd like
> > > to propose yourself again for this one ? Otherwise I'm happy to volunteer.
> > >
> > > Let me know what you think.
> > >
> > > Cheers
> > >
> > > Christophe
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Yunze Xu <yz...@streamnative.io.INVALID>.
I would like to include PIP-224 (even and PIP-229) in the next major
releases. These two PIPs have some impacts on the API and could bring
many benefits to ecosystem developers. But unfortunately the first PR
of PIP-224 [1] is still not reviewed by anyone. The code has already
been added locally and only requires some rebase to resolve conflicts.
[1] https://github.com/apache/pulsar/pull/19158
Thanks,
Yunze
On Fri, Jan 20, 2023 at 7:46 AM <ma...@gmail.com> wrote:
>
> Isn't the next version LTS 3.0?
>
> Best
> Mattison
> On Jan 20, 2023, 07:11 +0800, Christophe Bornet <bo...@gmail.com>, wrote:
> > Hi Pulsar community,
> >
> > It's great that we released Pulsar 2.11. It has taken quite some time to
> > stabilize the release branch and now we have more than 5 months of awesome
> > features and commits on the master branch that would benefit a lot to our
> > users. That's why I'd like to propose to start a code freeze for the
> > release of Pulsar 2.12 with a target release date by mid/end-february.
> > Hopefully this release will be easier to stabilize but we don't know for
> > sure, so better to start the release activities asap.
> > We also need a release manager. Nicolo proposed himself last time but had
> > to hand over because of his holiday schedule. So Nicolo, maybe you'd like
> > to propose yourself again for this one ? Otherwise I'm happy to volunteer.
> >
> > Let me know what you think.
> >
> > Cheers
> >
> > Christophe
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by ma...@gmail.com.
Isn't the next version LTS 3.0?
Best
Mattison
On Jan 20, 2023, 07:11 +0800, Christophe Bornet <bo...@gmail.com>, wrote:
> Hi Pulsar community,
>
> It's great that we released Pulsar 2.11. It has taken quite some time to
> stabilize the release branch and now we have more than 5 months of awesome
> features and commits on the master branch that would benefit a lot to our
> users. That's why I'd like to propose to start a code freeze for the
> release of Pulsar 2.12 with a target release date by mid/end-february.
> Hopefully this release will be easier to stabilize but we don't know for
> sure, so better to start the release activities asap.
> We also need a release manager. Nicolo proposed himself last time but had
> to hand over because of his holiday schedule. So Nicolo, maybe you'd like
> to propose yourself again for this one ? Otherwise I'm happy to volunteer.
>
> Let me know what you think.
>
> Cheers
>
> Christophe
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Christophe Bornet <bo...@gmail.com>.
>
>
>
> 2.11 has just been released and the release cycle is set to 3 months.
>
The release cycle wasn't really respected for 2.11...
We already have 5 months worth of features on the master branch and nothing
tells us that the release of 2.12 won't take 5 more months. And if we add 3
months to that...
>
> It's not a good idea to call for code freezes without appropriate
> warning, and code freezes don't make sense in general: the "master"
> branch must always be open for business.
> There was already a proposal to codify a formal release plan with
> prescribed timings for release RCs and stabilization.
> (https://github.com/apache/pulsar/issues/15966)
> It was actually discussed already very recently ((offline) that it's a
> good time to formally adopt it for the next release.
>
The code freeze I'm proposing is the one from this release plan. It's a
code freeze of the release branch, not of master.
Sorry if that was not clear. I used the word "code freeze" because that's
the one used in the PR. Maybe it's inappropriate and should be changed in
the PR.
Re: [DISCUSS] Code freeze for Pulsar 2.12
Posted by Matteo Merli <ma...@gmail.com>.
On Thu, Jan 19, 2023 at 3:11 PM Christophe Bornet
<bo...@gmail.com> wrote:
> It's great that we released Pulsar 2.11. It has taken quite some time to
> stabilize the release branch and now we have more than 5 months of awesome
> features and commits on the master branch that would benefit a lot to our
> users. That's why I'd like to propose to start a code freeze for the
> release of Pulsar 2.12 with a target release date by mid/end-february.
2.11 has just been released and the release cycle is set to 3 months.
It's not a good idea to call for code freezes without appropriate
warning, and code freezes don't make sense in general: the "master"
branch must always be open for business.
There was already a proposal to codify a formal release plan with
prescribed timings for release RCs and stabilization.
(https://github.com/apache/pulsar/issues/15966)
It was actually discussed already very recently ((offline) that it's a
good time to formally adopt it for the next release.