I kind of agree... But will this (not) affect how quickly new features in Luceneland will get their Solr support? In other words, if we have to wait for a proper Lucene release, doesn't that mean that:
1) Solr releases will depend on Lucene releases (unless there are some Solr-only changes that don't depend on newer version of Lucene) 2) Solr releases will lag Lucene releases quite a bit because only after Lucene has been released Solr developers/contributors will be able to start work on integrating new Lucene features into Solr? Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Yonik Seeley <[email protected]> > To: [email protected] > Sent: Thursday, June 25, 2009 7:18:31 AM > Subject: lucene releases vs trunk > > For the next release cycle (presumably 1.5?) I think we should really > try to stick to released versions of Lucene, and not use dev/trunk > versions. > Early in Solr's lifetime, Lucene trunk was more stable (APIs changed > little, even on non-released versions), and Lucene releases were few > and far between. > Today, the pace of change in Lucene has quickened, and Lucene APIs are > much more in flux until a release is made. It's also now harder to > support a Lucene dev release given the growth in complexity > (particularly for indexing code). Releases are made more often too, > making using released versions more practical. > Many of our users dislike our use of dev versions of Lucene too. > > And yes, 1.4 isn't out the door yet - but people often tend to hit the > ground running on the next release. > > -Yonik > http://www.lucidimagination.com
