atom feed19 messages in org.apache.lucene.general[VOTE] Merge the development of Solr/...
FromSent OnAttachments
Michael McCandlessMar 4, 2010 1:32 pm 
Michael McCandlessMar 4, 2010 1:34 pm 
Mark MillerMar 4, 2010 1:35 pm 
Simon WillnauerMar 4, 2010 1:40 pm 
Yonik SeeleyMar 4, 2010 1:42 pm 
Uwe SchindlerMar 4, 2010 1:45 pm 
Shalin Shekhar MangarMar 4, 2010 2:18 pm 
Andi VajdaMar 4, 2010 2:28 pm 
Robert MuirMar 4, 2010 2:42 pm 
Bill AuMar 4, 2010 3:06 pm 
Mattmann, Chris A (388J)Mar 4, 2010 3:11 pm 
Michael BuschMar 4, 2010 3:13 pm 
Chris HostetterMar 4, 2010 3:26 pm 
Koji SekiguchiMar 4, 2010 3:37 pm 
Grant IngersollMar 5, 2010 6:50 am 
Grant IngersollMar 5, 2010 11:14 am 
Ryan McKinleyMar 8, 2010 4:13 pm 
Chris HostetterMar 9, 2010 2:38 pm 
Erik HatcherMar 10, 2010 4:52 am 
Subject:[VOTE] Merge the development of Solr/Lucene (take 2)
From:Michael McCandless (luc@mikemccandless.com)
Date:Mar 4, 2010 1:32:52 pm
List:org.apache.lucene.general

A new vote, that slightly changes proposal from last vote (adding only that Lucene can cut a release even if Solr doesn't):

* Merging the dev lists into a single list.

* Merging committers.

* When any change is committed (to a module that "belongs to" Solr or to Lucene), all tests must pass.

* Release details will be decided by dev community, but, Lucene may release without Solr.

* Modulariize the sources: pull things out of Lucene's core (break out query parser, move all core queries & analyzers under their contrib counterparts), pull things out of Solr's core (analyzers, queries).

These things would not change:

* Besides modularizing (above), the source code would remain factored into separate dirs/modules the way it is now.

* Issue tracking remains separate (SOLR-XXX and LUCENE-XXX issues).

* User's lists remain separate.

* Web sites remain separate.

* Release artifacts/jars remain separate.

Mike