Better stick to Lucene snapshot versions. Commit the Lucene change first, then solr. If the Lucene change is not mature enough to commit to Lucene, it is probably not mature enough for Solr either. Avoid hacks or forks, spend some longer time to get it right.
If things get removed from Lucene and we want to support it in Solr for another major version, consider moving the code to solr git, under the Lucene package namespace. But it should not be something we do often. Jan >> 10. mai 2020 kl. 21:23 skrev Gus Heck <gus.h...@gmail.com>: > > >>> On Sun, May 10, 2020 at 11:55 AM Mike Drob <md...@apache.org> wrote: >> Solr maintaining a fork of Lucene sounds like exactly the situation that let >> to the original merge, where there are two sets of divergent development > > Exactly
