Hi All, -1 for the same reasons I mentioned previously. Again, I'm wearing my I'm-interested-in-this-discussion-but-not-a-Lucene/Solr-committer hat.
Cheers, Chris On 3/4/10 1:33 PM, "Michael McCandless" <luc...@mikemccandless.com> wrote: 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 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
