[hibernate-dev] Lucene 5.4 available: include it in a micro release?

[Sanne Grinovero]

Ok that was probably a foolish idea, especially like I'm realising
there wouldn't be a version range available like Guillaume Smet
suggests for people needing Lucene 5.3 but with additional fixes from
us.

Guillaume: still, this Lucene version could have equally been a
"micro"- if you except that Boost method set which is quite surprising
they removed them without even a single deprecation iteration. That
led me to think that it's probably not widely used.
Anyway: be aware that you could test Lucene 5.4 as a drop-in
replacement for 5.3, in case you're interested.

Andrej: are you needing that upgrade soon? Any interesting reasons?

If so we could already publish a quick Alpha version of 5.6: I'd label
it Alpha not because I think it's not stable but because the new
features which we're working on for 5.6 are not working yet; so as
long as you don't use them it should be fairly similar to an upgraded
5.5.x

Let us know ;)

Thanks,
Sanne


On 16 December 2015 at 19:18, Gunnar Morling <gunnar at hibernate.org> wrote:
> I'd prefer us to do this in a minor version, i.e. 5.6.
>
> As we expose Query to users, the removal of these methods may cause
> compilation errors on their side. Also the deprecation of Filter may
> cause many deprecations in client code.
>
> Both seem not appropriate for a micro release to me.
>
> I don't think we need to rush it. Compared to previous times, we are
> keeping up with new Lucene versions closely these days, so doing it
> during the envisioned 5.6 time frame seems fast enough to me. Or, if
> you really want to get it out sooner, we can do a quick 5.6 off
> master, I suppose prior to those first ES commits and release the
> latter as 5.7.
>
> --Gunnar
>
>
>
>
> 2015-12-16 14:22 GMT+01:00 Sanne Grinovero <sanne at hibernate.org>:
>> Hello all,
>>
>> Apache Lucene 5.4.0 is released as stable, and while it includes
>> several benefits - not least a performance fix from myself which I'd
>> be keen to take advantage of - there are no significant changes
>> visible to end users, expect I think this one is worth a warning:
>>
>>  LUCENE-6590: Query.setBoost(), Query.getBoost() and Query.clone() are
>> gone. In order to apply boosts, you now need to wrap queries in a
>> BoostQuery.
>>
>> Although, it doesn't affect any of our code not examples so a release
>> note might be acceptable.
>>
>> There are several other interesting performance improvements.
>> So I'm tempted to upgrade to this version in the next maintenance
>> (micro) release of Hibernate Search 5.5.
>>
>> What do you all think about that?
>>
>> Thanks,
>> Sanne
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev