There is a lingering discussion that comes to mind here: https://issues.apache.org/jira/browse/SOLR-2724 Title: Deprecate defaultSearchField and defaultOperator defined in schema.xml Essentially I committed this to 3x and trunk, trunk was subsequently reverted due to something else entirely, but before I re-committed to trunk, Yonik pipes in and says he doesn't agree with their deprecation (no vote up/down though). So… now what?
Speaking of deprecations, since this may be the last 3.x version, this means now is the time to send the right message to users on what may go away in a future Solr release. It's not clear to me if Solr 4 needs to guarantee compatibility with a Solr 3 configuration file or just aim for a likely probability of compatibility. ~ David On Apr 5, 2012, at 12:45 AM, Robert Muir wrote: > Please vote to release these artifacts: http://s.apache.org/lusolr36rc0 > > I tested with dev-tools/scripts/smokeTestRelease.py, ran rat-sources > on both source releases, tested solr example, and reviewed packaging > contents (http://people.apache.org/~rmuir/36_review/) > > Here's my +1. > > -- > lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
