[hibernate-dev] [HSEARCH] Any plan to release 3.4.2 soon?

Hardy Ferentschik hardy at hibernate.org
Mon Feb 13 10:38:49 EST 2012


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

--Hardy


On Feb 13, 2012, at 2:45 PM, Sanne Grinovero wrote:

> I think we should release one: we already backported some important
> fixes, especially because Guillaume helped with it (among others),
> which was very welcome.
> 
> So I can volunteer in making the release happen as I think such
> contributions should not be discouraged by lack of tag/release
> credentials, but I wonder if we should not fix some more issues on
> 3.4, especially one:
> I've seen some more people complaining about issues in Lucene
> specificially, and the 3.4 branch is using the rather old Lucene
> version 3.1.
> 
> https://hibernate.onjira.com/browse/HSEARCH-885
> 
> So I think we should solve that, and interestingly enough we can just
> bump the version from Lucene 3.1 to 3.4 without any code change, or to
> get 3.5 backporting one patch.
> What puzzles me more if we should actually update Lucene in a minor
> version - that was not our custom in the past, but previously Lucene
> would take much longer for a new version and use minor versions (I
> remember upgrading to 2.4.1, 2.4.2, 2.4.3 ..) while now the Lucene
> team seems to have changed strategy and are doing 3.1.0, 3.2.0, ..
> 3.5.0 : so could we consider it acceptable to upgrade the Lucene
> version in HS 3.4.2 ?
> 
> Options:
> 1- not upgrade at all
> 2- bump Lucene to 3.4.0
> 3- Upgrade to Lucene 3.5.0 : Needs someone to volunteer in backporting
> the needed code changes.
> 
> What do you think?
> 
> The only other nasty bug on 3.4.0 is HSEARCH-975: if someone takes
> responsibility on it we can include it, or it will wait for next. TBH
> I don't think we can solve it without moving JGroups to a separate
> module(s), and might not be worth the effort since it's not an issue
> in 4.x.
> 
> Cheers,
> Sanne
> 
> 
> On 13 February 2012 13:08, Emmanuel Bernard <emmanuel at hibernate.org> wrote:
>> Sanne, Hardy and I don't have specific plans to release a 3.4.x. Our general strategy is to support the latest stable branch and do new work on the next version. Older branches are out of this equation.
>> 
>> But we are not against the community doing the work. A release is a bit of an extreme as it requires several credentials but we can think of something. What do you all think?
>> 
>> On 11 févr. 2012, at 19:22, Guillaume Smet wrote:
>> 
>>> Hi Hibernate Search developers,
>>> 
>>> Is there any plan to release 3.4.2 soon?
>>> 
>>> We especially would like to see HSEARCH-1020 released in an official
>>> 3.4.x release as we have a couple of applications in production we
>>> won't move to 4.x. I would like to remove the workaround we added (we
>>> define a non default boost strategy to force reindexing entities on
>>> update... cough cough...)
>>> 
>>> Thanks for your feedback.
>>> 
>>> --
>>> Guillaume
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> 
>> 
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> 
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev





More information about the hibernate-dev mailing list