The question came up in the context of a discussion about whether it could be sensible for Lucene 9.0 to be released without Solr 9.0 being released. I think we're struggling a bit to conceptualize how the next release will work: release 9.0 as we do today and delay the split until after, coordinate the releases of Lucene 9.0 and Solr 9.0, but separately, or try to decouple them somehow.
On Thu, Jan 14, 2021 at 1:20 PM Adrien Grand <[email protected]> wrote: > > Le jeu. 14 janv. 2021 à 18:16, Mike Drob <[email protected]> a écrit : >> >> >> 9.0 Release Planing >> >> Reminder that there are issues with new minors after a major release (8.9 >> after a 9.0) - somebody to research. > > > The main challenge with this is backwards compatibility testing. If you > release 8.9 after 9.0, there is nothing in the release process that tests > that Lucene 9 can read 8.9 indices even though that is a guarantee we > provide. It can be tested manually (we have done it a couple times) but this > is quite painful and not as reliable as having it tested on every CI build > prior to the release, so we prefer avoiding releasing new minors after a new > major. > > This is mostly a problem for Lucene so once Lucene and Solr have distinct > release cycles, Solr could potentially do this, e.g. release Solr 9.9 after > 10.0 is out (as long as Solr 9.9 keeps depending on the same Lucene version > as Solr 9.8). > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
