In Relation To

These releases contain mostly minor bugfixes and improvements. For more information, please see:

You can now upgrade to Version 5.0.0.Beta3 of Hibernate Search, and benefit from the following improvements:

For more information, please see:

We are getting closer to a final release and this version is mainly about improving general performance and reducing the amount of round trips to the datastore. We also added optimistic locking support for datastores which provide atomic find-and-update operations.

For more information, please see:

Hibernate ORM 4.2.14.Final was just released! Please see the full changelog for more information: https://hibernate.atlassian.net/issues/?jql=project=10031+AND+fixVersion=17152.

Hibernate ORM 4.2.13.Final was just released! Please see the full changelog for more information: https://hibernate.atlassian.net/issues/?jql=project=10031+AND+fixVersion=16650.

Hibernate ORM 4.2.12.Final was just released! Please see the full changelog for more information: https://hibernate.atlassian.net/issues/?jql=project=10031+AND+fixVersion=16350.

Hibernate ORM 4.3.5.Final was just released! Please see the full changelog for all the details: https://hibernate.atlassian.net/issues/?jql=project=10031+AND+fixVersion=16251. As usual, big thanks to the community for several contributions!

What do you get from a 10+ year old open source framework, thousands of users within a wide range of roles, and complexity? A JIRA instance with over 3,000 unresolved tickets ;). Is that number indicative of low software quality? Definitely not. But therein lies the problem. A vast majority of the tickets are no longer issues, no longer relevant, or duplicates. Due to the quantity, it became nearly impossible to weed through them all.