You chose correctly. Unless you are sure, picking one beyond current RC in progress is good, because when RMs sweep JIRA just prior to release and will adjust fix versions as needed, but the reverse is not true... if you concurrently/independently set a fix version to something not in the RC the RM will likely not notice.
On Thu, Jun 23, 2022 at 1:55 PM Bryan Beaudreault <bbeaudrea...@hubspot.com.invalid> wrote: > Sounds good! I'm not super clear on the release process. I just merged > something to branches 2.5 and 2.4. I set the Fix Versions to 2.5.1 and > 2.4.14, because I know you're actively working on the release for these and > imagine you might have already created a tag. Was that correct, or should I > change to 2.5.0 and 2.4.13 respectively? Jira in question: > https://issues.apache.org/jira/browse/HBASE-26945 > > Thanks for your guidance > > On Thu, Jun 23, 2022 at 11:17 AM Andrew Purtell <andrew.purt...@gmail.com> > wrote: > > > Thank you for thinking of a pause, but that should not be necessary. > > > > > On Jun 23, 2022, at 3:40 AM, Bryan Beaudreault < > bbeaudrea...@hubspot.com.invalid> > > wrote: > > > > > > Thank you for your hard work and thoroughness here. > > > > > > Should we pause merging to branch-2.4 until you wrap this? I have some > > > things I could merge in the near future, but they are not urgent so I’m > > > happy to wait to backport to 2.4 if it will help. > > > > > >> On Wed, Jun 22, 2022 at 11:10 PM Andrew Purtell < > > andrew.purt...@gmail.com> > > >> wrote: > > >> > > >> Expect to begin voting at 2.4.13RC1, because while testing RC0 found > two > > >> issues: > > >> > > >> First, there is a new repeatable unit test failure, > > >> TestMultiRespectsLimits, which passes at rel/2.4.12. See HBASE-27151 > > for > > >> more information. The cause identified by git bisect, HBASE-26856, has > > been > > >> reverted from branch-2.4 for now. > > >> > > >> Second, we forgot to cherry pick to branch-2.4 HBASE-27050, the change > > that > > >> makes surefire work with wildcards again, which would not sink a > > release on > > >> its own but is annoying and because there must be a RC1 anyway we can > > >> include it. > > >> > > >> > > >> On Wed, Jun 22, 2022 at 8:04 AM Andrew Purtell < > > andrew.purt...@gmail.com> > > >> wrote: > > >> > > >>> Because this issue is already present in 2.4 and there is another fix > > >>> requiring release I am going to proceed with 2.4.13. The > > SimpleRpcServer > > >>> fix can land in 2.4.14. It remains a blocker for 2.5.0. > > >>> > > >>>> On Jun 18, 2022, at 8:13 AM, Andrew Purtell <apurt...@apache.org> > > wrote: > > >>> > > >>> > > >>> HBASE-27097 was reopened because of a continuing issue when > > >>> SimpleRpcServer is configured and SASL is enabled. > > >>> > > >>> > > >>> > > >>> On Sun, Jun 12, 2022 at 11:10 AM Andrew Purtell <apurt...@apache.org > > > > >>> wrote: > > >>> > > >>>> HBASE-25709 introduced a regression, has been reverted, and now we > > need > > >> a > > >>>> release. > > >>>> > > >>>> In addition SimpleRpcServer was found to have a serious bug, fixed > in > > >>>> HBASE-27097, committed to branch-2.4 as well. > > >>>> > > >>>> -- > > >>>> Best regards, > > >>>> Andrew > > >>>> > > >>> > > >>> > > >>> -- > > >>> Best regards, > > >>> Andrew > > >>> > > >>> Unrest, ignorance distilled, nihilistic imbeciles - > > >>> It's what we’ve earned > > >>> Welcome, apocalypse, what’s taken you so long? > > >>> Bring us the fitting end that we’ve been counting on > > >>> - A23, Welcome, Apocalypse > > >>> > > >>> > > >> > > >> -- > > >> Best regards, > > >> Andrew > > >> > > >> Unrest, ignorance distilled, nihilistic imbeciles - > > >> It's what we’ve earned > > >> Welcome, apocalypse, what’s taken you so long? > > >> Bring us the fitting end that we’ve been counting on > > >> - A23, Welcome, Apocalypse > > >> > > > > > -- Best regards, Andrew Unrest, ignorance distilled, nihilistic imbeciles - It's what we’ve earned Welcome, apocalypse, what’s taken you so long? Bring us the fitting end that we’ve been counting on - A23, Welcome, Apocalypse
