Just going to throw this out there, but I don’t think you have to know much
of anything about the likely quality and impact of changes from Lucene 9.1
to say that raising the king dependency for a software project by a full
dot release is def not “respin and another quick round of smokes material”
even if this wasn’t an abnormal major release train.

I can’t imagine how you wouldn’t want to add some meaningful breathing room
gap even with the best of confidence in those changes and all the ways they
might interact with Solr.

Maybe that breathing room shows up anyway due to unrelated issues along the
lines of SQL support, but seems to me the total potential impact gamble
pretty easily says you’d want to bake that time into your vote to pull that
trigger regardless.



Mark

Reply via email to