If we agree that this warrants a patch release, I volunteer to do the release.
I do think a patch release is reasonable even if users have to take an action when upgrading from 8.6.0. I imagine most users haven't upgraded to 8.6.0 yet, so if we make the patch now we will make life easier for everyone that upgrades between now and when 8.7 is released. On Wed, Jul 22, 2020 at 12:50 PM Atri Sharma <[email protected]> wrote: > Ignore this, I misread your email. > > On Wed, Jul 22, 2020 at 9:11 PM Atri Sharma <[email protected]> wrote: > > > > Should we not revert the change so that users upgrading from 8.6 to > > 8.6.1 get the earlier default policy? > > > > On Wed, Jul 22, 2020 at 9:09 PM Houston Putman <[email protected]> > wrote: > > > > > > +1 > > > > > > Question about the change. Since this patch added a default > autoscaling policy, if users upgrade to 8.6 and then 8.6.1, does the > default autoscaling policy stay once they have upgraded? If so we probably > want to include instructions in the release notes on how to fix this issue > once upgrading. > > > > > > - Houston > > > > > > On Wed, Jul 22, 2020 at 1:53 AM Ishan Chattopadhyaya < > [email protected]> wrote: > > >> > > >> Hi, > > >> There was a performance regression identified in 8.6.0 release due to > SOLR-12845. I think it is serious enough to warrant an immediate bug fix > release. > > >> > > >> I propose a 8.6.1 release. Unfortunately, I'll be unable to volunteer > for this release owning to some other commitments, however Andrzej > mentioned in Slack that he might be able to volunteer for this post 27th. > > >> > > >> Are there any thoughts/concerns regarding this? > > >> Regards, > > >> Ishan > > > > -- > > Regards, > > > > Atri > > Apache Concerted > > > > -- > Regards, > > Atri > Apache Concerted > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
