Matteo,
Can you start the vote for this PIP?
We should start working on 3.0.0 soon and this PIP is required to
reach community consensus.
https://lists.apache.org/thread/d6rk2ntzwk8twznf82k7o6xgyb2k9s14
Thanks,
Nicolò Boschi
Il giorno mer 9 nov 2022 alle ore 09:37 Haiting Jiang <
jianghait...@
Hi all,
What's status of this PIP?
There's an issue talking about fixable vulnerabilities in the latest release.
https://github.com/apache/pulsar/issues/18348
>From what I see, one of the problems is that we take too long to make a new
>release ( over 2 months for 2.10.2 ). Hopefully, this PIP
1. We can compose some charts/tables as https://endoflife.date/python on
the Pulsar website to help people understand the time frame.
2. Regarding the LTS release proposal, one thing I need some clarification
is will the LTS release include major new features compared to last release?
For exam
> From the code-freeze point, to minimize the risk of delaying the
> release, only bug fixes involving a regression of behavior compared to
> a previous release should be allowed. Occasional exceptions will be
> possible after higher scrutiny of the change.
It's a frequent point of discussion to d
> Schedules always slip. Would you say that if the 3.x feature releases take
> too long with these hypothetical dates that 3.5 would be dropped in order to
> release 4.0 on schedule?
Yes, there needs to be clarity for the users on when releases are to
be expected, even more so for LTS releases.
> On Jun 8, 2022, at 11:44 AM, Matteo Merli wrote:
>
> On Tue, Jun 7, 2022 at 10:14 PM PengHui Li wrote:
>>
>> I'm not sure I fully understand the LTS release and feature release.
>>
>>> The LTS releases will be identified by being a `.0` version. For example:
>>> * `3.0` -> LTS
>>> * `3.1`
--
Matteo Merli
On Wed, Jun 8, 2022 at 12:33 AM Haiting Jiang wrote:
>
> > I was actually not thinking of changing the denomination of 2.11. On
> > one hand, it could make sense for being the first Java 17 release, but
> > on the other, we'd be releasing 2 LTSs super close between each other
>
On Tue, Jun 7, 2022 at 10:14 PM PengHui Li wrote:
>
> I'm not sure I fully understand the LTS release and feature release.
>
> > The LTS releases will be identified by being a `.0` version. For example:
> > * `3.0` -> LTS
> > * `3.1` -> regular release
> > * `3.2` -> regular release
> > * `4.0` ->
> I was actually not thinking of changing the denomination of 2.11. On
> one hand, it could make sense for being the first Java 17 release, but
> on the other, we'd be releasing 2 LTSs super close between each other
> and we'd have to support 1 release more for the time being.
>
> I'd like to hea
I'm not sure I fully understand the LTS release and feature release.
> The LTS releases will be identified by being a `.0` version. For example:
> * `3.0` -> LTS
> * `3.1` -> regular release
> * `3.2` -> regular release
> * `4.0` -> LTS
In this example, we can only introduce new features in 3.1 a
Thanks for putting together this PIP to continue this discussion,
Matteo. This is an important one.
I'll need time to think over your points before I respond, but I want
to address two of them right away.
> Actually, I was wrong. PIP-47 says the last 4 releases so 2.7 would be
> included.
> The
> > There is a high cost to maintain a lot of old releases, backport bug
> > fixes, and security patches. In general, we actively support the last
> > 3 minor releases while continuing to develop the next release. E.g.,
> > 2.8, 2.9, and 2.10, while 2.11 is under development.
>
> Is 2.7 EOL? If so
Hi -
Interesting, some responses inline.
> On Jun 7, 2022, at 3:25 PM, Matteo Merli wrote:
>
> https://github.com/apache/pulsar/issues/15966
>
>
>
> ## Motivation
>
> In PIP-47
> (https://github.com/apache/pulsar/wiki/PIP-47:-Time-Based-Release-Plan),
> we have adopted a time-based
https://github.com/apache/pulsar/issues/15966
## Motivation
In PIP-47
(https://github.com/apache/pulsar/wiki/PIP-47:-Time-Based-Release-Plan),
we have adopted a time-based release plan. This was the first attempt
at establishing a new principle on how releases should b
The main two be
14 matches
Mail list logo
