On Tue, Mar 9, 2010 at 7:41 AM, Yonik Seeley <ysee...@gmail.com> wrote:
> > Mike's call for a VOTE (amongst lucene/solr committers +11 to -1): > > http://search.lucidimagination.com/search/document/a400ffe62ae21aca/vote_merge_the_development_of_solr_lucene_take_2#22d7cd086d9c5cf0 > > Subject: Merge the development of Solr/Lucene (take 2) > > 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. > +1 I think that, in the long term, this move will prove beneficial for both the projects. -- Regards, Shalin Shekhar Mangar.
