+1 to the plan - Henry
On Tue, May 25, 2021 at 1:51 PM Andrey Yegorov <ayego...@apache.org> wrote: > I am ok releasing 4.14.1 now. > I have finalized all the steps for the 4.14: updated the site etc. > I will NOT send an email about the 4.14.0 release and we'll use 4.14.1 > to notify the community to limit the distribution of the build with > the blocker. > > Does it sound ok to you? > > On Tue, May 25, 2021 at 8:39 AM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > > Il giorno mar 25 mag 2021 alle ore 17:15 Matteo Merli > > <mme...@apache.org> ha scritto: > > > > > > On Tue, May 25, 2021 at 6:00 AM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > > Before rushing to a release, isn't it better to wait for a couple of > > > > weeks in order to see > > > > if other people in the community find other problems on 4.14.0 > > > > > > As it is, the 4.14.0 release cannot be used by Pulsar. At the same > > > time, there are blocker issues for the upcoming Pulsar 2.8.0 that are > > > only fixed in the BK 4.14 branch. > > > > > > I don't think that waiting 2 weeks will help at all here. We already > > > have a blocker issue, which is already fixed and that could unblock > > > 4.14 and Pulsar 2.8. > > > > > > > AFAIK BK 4.14.0 has not been announced yet publicly > > > > > > Since we cannot change 4.14.0 at this point (the vote was cast, the > > > jars are in maven central), I don't think that it would be a problem > > > to just announce 4.14.1 directly, since the 4.14.0 is not usable. > > > > I agree. > > > > Enrico > > > > > > > > Matteo >
