On Thu, 26 Sept 2024 at 09:49, Yubiao Feng
wrote:
> - I think `3.0` is a long-term supported version, since the PIP is very
> useful, I want to cherry-pick it into `branch-3.0`
> - `3.3` is not a long-term supported version, so the PIP will be released
> with the next feature release quickly, so I
Hi Lari
> Why did we cherry-pick to branch-3.0
> but skip branch-3.3?
- I think `3.0` is a long-term supported version, since the PIP is very
useful, I want to cherry-pick it into `branch-3.0`
- `3.3` is not a long-term supported version, so the PIP will be released
with the next feature release
One more question about this. Why did we cherry-pick to branch-3.0, but skip
branch-3.3?
Usually we cherry-pick to all maintenance versions along the way if we do
cherry-picks.
What is the reason to skip branch-3.3 in this case?
-Lari
On 2024/08/26 02:27:58 Yubiao Feng wrote:
> Hi all
>
> I wo
Hi all
Cherry-picked.
Thanks
Yubiao Feng
On Mon, Aug 26, 2024 at 10:27 AM Yubiao Feng
wrote:
> Hi all
>
> I would like to start a discussion to cherry-pick PIP-370 into `branch-3.0`
>
> This PIP is very useful for the scenario of managing topics manually, it
> provides a metric that is useful
Makes sense.
-Lari
On 2024/08/26 02:27:58 Yubiao Feng wrote:
> Hi all
>
> I would like to start a discussion to cherry-pick PIP-370 into `branch-3.0`
>
> This PIP is very useful for the scenario of managing topics manually, it
> provides a metric that is useful to monitor whether the replicator
Hi all
I would like to start a discussion to cherry-pick PIP-370 into `branch-3.0`
This PIP is very useful for the scenario of managing topics manually, it
provides a metric that is useful to monitor whether the replicators work as
expected, and the default behavior changed nothing, we can gracef
