On Tue, Mar 16, 2010 at 1:47 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > even if we get Lucene-Java and Solr onto the same > scheme now, we could easily find ourselves in a situation where > we're ready to release lucene-3.3 (ie: a minor release that is > back-compat with lucene-3.2 and addss some new features) but we also want > to release a new "major" version of solr that breaks compatibility with > solr-3.2 ... so what do we call that?
We try not to do that then. Things make a lot more sense when one starts thinking of them as a single project, w/o multiple downloads. If major modules were to be pulled from Solr and put into Lucene, and Solr wanted to make some big changes for a major version number bump? How could it do so w/o lucene doing that? It's the same issue. -Yonik
