I would recommend to adopt your app to 2.9 and enable deprecation warnings. As soon as all deprecation warning disappear during compile, you are able to just go to 3.0 (just drop in jars when available). This is why we have 2.9. 2.9: it is just 3.0 with the deprecations not yet removed. No other changes extensions to the API.
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Ivan Vasilev [mailto:ivasi...@sirma.bg] > Sent: Friday, October 16, 2009 11:59 AM > To: LUCENE MAIL LIST > Subject: is Lucene 3.0 coming soon? > > Hi Lucene Guys, > > I am interested what is your plan date for releasing Lucene 3.0. > I am asking because seeing on the changes in Lucene 2.9 (especially > changes in backward compatibility) I guess that it will be difficult for > us to adopt our app to Lucene 2.9. I see in your Jira there are not many > issues planned for 3.0, but there are still some new deprecations > removing. There also could come some bug fixes to 2.9. So if you plan to > release 3.0 in some (3-4) months we prefer to adopt our app directly to > 3.0. > > Another question about your plans about changes in file structure. > According to your backwards-compatibility policy Lucene 3.0 could be not > able to read indexes created from Lucene 1.X. Will it be really so with > 3.0? > > Best Regards, > Ivan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
