That makes sense, I can target that for 9.12, would that makes sense? > On Sep 3, 2026, at 11:47 AM, Eric Pugh <[email protected]> > wrote: > > There is a, well, at least a hope, that we’ll get a 9.12 out much sooner > than it has taken for 9.11. So I would prefer not to delay the 9.11 for > this. > > Let’s land this when it’s ready! > > > >> On Sep 3, 2026, at 12:35 PM, Arup Chauhan <[email protected]> >> wrote: >> >> I have a suggestion before we release 9.11. >> >> Recently, while working with the JMH harness on JDK 21, I noticed that we >> still pass JVM flags related to biased locking (UseBiasedLocking). Biased >> locking was disabled by default and deprecated starting with JDK 15, and the >> associated flags were later made obsolete. >> >> Would it make sense to add a JDK version check in the JMH harness and avoid >> passing these flags on JDK versions where they are no longer applicable? >> >> My reasoning is that this is particularly relevant for Solr 9.x. Solr 10 >> already requires JDK 21, but there are likely still many users on Solr 9.x >> who have upgraded their JDK independently. In that case, the benchmark >> harness can run into compatibility issues because of JVM flags that were >> intended for older JDKs. >> >> Since we are approaching the 9.11 release, I thought this might be a useful >> compatibility fix to include before the release if you think it makes sense. >> >>>> On Sep 3, 2026, at 10:50 AM, David Smiley <[email protected]> wrote: >>> >>> I am resuming the 9.11 release, intending to issue an RC on September 11th. >>> I will re-create branch_9_11 Monday EOD, EST. >>> >>> I will do my usual backporting immediately prior to cutting that release, >>> and I will *not* gate it on passing CI. Thus anything merged to main by >>> Monday and with a 9.x milestone will make it into 9.11. I'll run tests >>> locally. >>> >>> ~ David Smiley >>> Apache Lucene/Solr Search Developer >>> http://www.linkedin.com/in/davidwsmiley >>> <http://www.linkedin.com/in/davidwsmiley> > > Disclaimer > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and others > authorized to receive it. If you are not the recipient, you are hereby > notified that any disclosure, copying, distribution or taking action in > relation of the contents of this information is strictly prohibited and may > be unlawful. > > This email has been scanned for viruses and malware, and may have been > automatically archived by Mimecast, a leader in email security and cyber > resilience. Mimecast integrates email defenses with brand protection, > security awareness training, web security, compliance and other essential > capabilities. Mimecast helps protect large and small organizations from > malicious activity, human error and technology failure; and to lead the > movement toward building a more resilient world. To find out more, visit our > website.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
