Il giorno gio 2 feb 2023 alle ore 08:08 Haiting Jiang
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
> 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 officiall
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 wrote:
> From my understanding we should follow PIP-175.
> Actually it has not been officially voted on but we can address that
> easily.
>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
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 a écrit :
> Christophe,
>
> Given the Chinese New Year
>
>
>
> 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 th
On Thu, Jan 19, 2023 at 3:11 PM Christophe Bornet
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
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 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 ca
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 wrote:
>
> I would li
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 an
Isn't the next version LTS 3.0?
Best
Mattison
On Jan 20, 2023, 07:11 +0800, Christophe Bornet , 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 com
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 f
12 matches
Mail list logo
