Since there's going to be one more release candidate for 3.2.0 , I have cherry-picked PIP-326 (pulsar-bom) to branch-3.2. pulsar-bom is a low risk addition to the release.
-Lari On 2024/01/18 17:54:22 Chris Bono wrote: > The Pulsar BOM (PIP-326) implementation missed the initial timeline to > be included in the 3.2.0 release. > > It seems like an RC2 may be needed for a couple of new Bookkeeper bugs: > * https://lists.apache.org/thread/tcy93c8vrb475j64tdotlklxblrcm728 > * https://github.com/apache/pulsar/issues/21421 > > This thread is not to discuss the above bugs or if a 2nd RC is needed, > but rather IFF a 2nd RC is decided upon would there be any objections > to also include the Pulsar BOM > (https://github.com/apache/pulsar/commit/176bdeacd309e8c1e49358987a1946abd30ba34a) > in the RC2? This is an entirely additive change (new module not used > by any other modules) and poses very low risk to the release. > > Any objections? > > Thanks, > Chris >
