Hi Ganesh I recently upgraded my code to 3.6, and yesterday finished part of my upgrades to 4.0-ALPHA.
Upgrading from 3.0.3 to 3.6 is relatively easy as all API should be backwards compatible. But I think there were some API breaks, and back-compat issues. Therefore, if I were you, I'd first upgrade from 3.0.3 to 3.6, resolving all 'deprecated' API warnings and making sure the back-compat issues do not affect me (or resolve them too !). Then, I'd upgrade to 4.0-ALPHA. A lot of API has been changed, and so most likely you'll need to touch large parts of your code again. Going this route, you gain all the new features and enhancements of 3.6, while knowing that you run on a 'stable' Lucene version. Upgrading to 4.0-ALPHA comes with even more gains, but this release will probably go under some API changes (API is expected to freeze in BETA), though the index format is not going to change in incompatible ways (unless there's a bug ... you can read the release notes), so depending on how much you want to risk doing the upgrade for a still 'work in progress' code. Hope this helps. Shai On Tue, Jul 10, 2012 at 7:28 AM, Ganesh <emailg...@yahoo.co.in> wrote: > Hello all, > > I am currently using v3.0.3 and planning to upgrade to v3.6. Shall i go > ahead with the upgrade OR wait for 4.0? > > Regards > Ganesh > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
