On Tue, Mar 16, 2010 at 10:45 AM, Grant Ingersoll <gsing...@apache.org> wrote: > > On Mar 16, 2010, at 11:00 AM, Yonik Seeley wrote: > >> Here is a very rough list of what makes sense to me: >> - since lucene is on a new major version, the next solr release >> containing that sould have a new major version number >> - this does not preclude further releases on 1.x >> - for simplicity, and the "single dev" model, we should just sync >> with lucene's... i.e. the next major Solr version would be 3.1 >> - branches/solr would become the new trunk, with a shared trunk with >> lucene in some structure (see other thread) >> - solr cloud branch gets merged in >> - we move to Java6 (Java5 has already been EOLd by Sun unless you pay >> money... and we need Java6 for zookeeper, scripting) > > Hmm, how does that effect Lucene, though? It is only on 1.5.
Same way it did when lucene core was 1.4 but some of the contribs were 1.5 i.e. I don't think it really should affect anything. Lucene core moving to 1.5 is a different decision. -Yonik
