Thanks for bringing it up Dawid. I’ve asked myself the same question several times over the last couple of years, and have kind of been waiting for someone to make the proposal :) In my head, Solr has out-grown being a sub project of Lucene, like hadoop, mahout, nutch and tika before it.
The move will promote Solr as a separate TLP with better visibility and more autonomy. Simply put Solr will go from https://lucene.apache.org/solr/ to https://solr.apache.org/ Splitting will be lots of work for sure, but I am not worried about the future relationship between the two. The last couple of years most og us have already done LUCENE and SOLR changes in separate Jiras and separate patches, first committing changes to LUCENE before the related SOLR change. It will be more or less the same approach after the split, just that there will be a couple of days between the Lucene release and the next Solr release depending on it. As it is today, deveopers have had to do necessary Solr changes at the same time when doing changes in Lucene. This is not really fair to the (mainly) Lucene developers. It is not fair to Solr either, as such work might be done in a hasty fashion and/or in a sub optimal way due to lack of familiarity with Solr code base; like we unfortunately have seen a couple of times in the past (not trying to blame anyone). With Lucene as a dependency, Solr can choose to stay on same Lucene version for a couple of releases while taking the time to work out the proper way to adapt to changed Lucene APIs or to sort out performance issues. Question: When Lucene no longer has the Solr test suite to help catch bugs, how long time would it take from a Lucene commit, before Solr/ES Jenkins instances would have had time to produce a build and run tests? Would it be possible to setup a trigger in Solr Jenkins? Jan > 4. mai 2020 kl. 11:10 skrev Dawid Weiss <dawid.we...@gmail.com>: > > Dear Lucene and Solr developers! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
