> In general, these problems hint to me that we need better definitions
> for "system" and "special" topics that break the rules of auto created
> topics in well defined ways.
This point reminds me of this discussion from a year and a half ago:
https://lists.apache.org/thread/qgbpzr6o3k5rqbs2jvpk
Hi Pulsar Community,
I recently noticed this page on our website:
https://pulsar.apache.org/contribute/release-policy/#supported-versions
It shows that only 2.11 and 3.0 are active and security support.
I am guessing the timelines were taken from a strict reading of PIP
47. However, we haven't h
Thanks for this discussion, Lari. I agree with your points and will
just make a few additions.
@Lari - I wonder if there is a way we can show the strategy more
definitively. Have you looked into what it would take to merge
branch-3.0 to master? If that is too hard, we could pilot merging
branch-3.
After several ping pongs over the PR, I'm changing my vote:
+1 (non-binding)
Just please make sure to review all pending grammar suggestions.
On Tue, Jun 6, 2023 at 10:53 PM Asaf Mesika wrote:
> I'm sorry for not getting back to you sooner: Weekend, work, etc.
>
> I vote -1 (non-binding), as I
Hi Lari,
Thanks for starting this discussion! I did some cherry-picking recently and
encountered a few cases
that can be noted in your email. The most surprising process to me is that
we pick commit directly
without any regression tests (some is associated with PRs, but it's not the
normal case).
