So to take a decision on this, are we going to stick with the current Lucene version in the 3.4 branch ?
Basically means to reject https://hibernate.onjira.com/browse/HSEARCH-885 -- Sanne On 13 February 2012 17:04, Guillaume Smet <guillaume.s...@gmail.com> wrote: > Hi, > > On Mon, Feb 13, 2012 at 4:38 PM, Hardy Ferentschik <ha...@hibernate.org> > wrote: >> I am fine with a 3.4.2. I don't think we should put too much effort into it >> ourself, but rely on the >> community if they want more features back ported. >> >> +1 for upgrading to Lucene 3.4.0 > > I don't think you can upgrade to Lucene > 3.3 without backporting the > mass indexer changes Sanne commited. Otherwise you'll get a really > significant performance regression. > > HSEARCH-1020 was a regression from 3.3 to 3.4 because of the > performance improvements done in 3.4. I don't think an upgrade to a > new version of Lucene is something to do in a point release. > > Concerning the release policy, keep in mind that a lot of person will > continue to have Hibernate 3.6.x + Hibernate Search 3.4.x in > production for a while as moving to 4 is a significant move. > Our new applications are based on 4 but we still have old ones in > production and it's always better to use an official release than a > custom one. > > Typically, I won't ask a point release for 4.0.x as we're going to > move to 4.1.x but it seems to me a good idea to be sure that 3.6.x and > 3.4.x have final point release versions which are rock solid. > > My 2 cents as an end user. > > -- > Guillaume > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
