We definitely want https://github.com/apache/pulsar/pull/10413 included in 2.7.2 since it improves thread safety.
-- Devin G. Bost On Fri, Apr 30, 2021, 1:01 AM Enrico Olivelli <eolive...@gmail.com> wrote: > Il giorno gio 29 apr 2021 alle ore 20:57 Sijie Guo > <guosi...@gmail.com> ha scritto: > > > > Can you include these two issues? I have marked them for 2.7.2. > > Sure, Penghui committed them. > > > There are a few problems on branch-2.7 due to last minute cherry-picks > > I am sending PRs for fixes > for instance this is a fix for a test that relied on "memory" > MetadataStore, that is not available on branch-2.7 > > https://github.com/apache/pulsar/pull/10453 > > Enrico > > > > > > https://github.com/apache/pulsar/pull/10420 > > https://github.com/apache/pulsar/pull/10416 > > > > Thanks, > > Sijie > > > > > > On Thu, Apr 29, 2021 at 12:32 AM Enrico Olivelli <eolive...@gmail.com> > > wrote: > > > > > Hi fellows, > > > I am preparing 2.7.2, > > > > > > I saw in this issue that Matteo added the label "release/2.7.2" and > > > merged the issue to master branch. > > > https://github.com/apache/pulsar/pull/10413 > > > > > > Unfortunately in this case the PR is "closed" and marked for 2.7.2 so > > > it looks like it has been committed to 2.7.2, but it is not true. > > > > > > Apart from that specific case, > > > it is important to ping me directly if there is something that you > > > want to include in 2.7.2. > > > > > > Otherwise the risk is that something that you think is in 2.7.2 it is > not > > > :-) > > > > > > I am verifying the commit log and checking for possible problems of > this > > > kind. > > > > > > I had to wait for a couple of blocker issue before proceeding for the > > > release, > > > not AFAIK it is time to proceed > > > > > > Enrico > > > >
