[hibernate-dev] [Search] Regression with @ContainedIn between 4.3 and 4.4

Guillaume Smet guillaume.smet at gmail.com
Fri Mar 28 08:28:18 EDT 2014

Hi Sanne,

On Fri, Mar 28, 2014 at 12:56 PM, Sanne Grinovero <sanne at hibernate.org> wrote:
> However - I might not have fully grasped this yet - but I'm thinking
> that this is a feature request and not a bugfix that should be hastily
> applied on 4.4.

It's not a feature request. 4.4 changed this behavior. It was working
well with 4.3 (and every other versions before that).

> Guillaume, I suspect you might be a happier user if you would keep
> using a more bleeding edge version, so to catch any such thing earlier
> rather than the day before you go in production. I can only promise
> you that the migration to 5.0 will be a nightmare if you don't follow
> along in small iterations :-(

I don't think we can be more bleeding edge than us. We upgrade our
core framework to new versions as soon as they are released (we coded
https://www.artifact-listener.org/ for this purpose). That's why we
spend a considerable amount of time doing QA on the components we use
- you see a part of this work on ORM + Search but we also do it for
other components. You might have noticed that we are often the first
company out there to catch regressions.

When we have the ability to dedicate cycles to it, we also test CR.

But... we develop a lot of applications for a lot of customers and
they have different lifecycles: we can upgrade some easily and for
others we have to wait for the right opportunity to do it.

All in all, we have the following policy:
- all the applications in development: they use the latest versions of
each components, except if we catch a regression when upgrading. If so
we try to help fix it for the next version and we upgrade ASAP;
- the applications in production are updated regularly for minor
changes; If the changes are big, we wait for our customers to ask
changes on the app and we do it then.

The fact is that we caught this one while upgrading an app which was
using 4.3.0.Final (which is not that old) but I think we have other
applications already upgraded to 4.4.2 which have that bug, it's just
that we haven't caught it when we upgraded.

FWIW, we couldn't upgrade to 4.4.x before 4.4.2.Final because of a few
regressions we reported and helped getting fixed (I have at least
these ones in mind: HSEARCH-1442 and HSEARCH-1462 but IIRC we had

(Sorry for the noise but I thought it was a good opportunity to
explain how we work, considering we're involved in this community for
quite a long time now)


More information about the hibernate-dev mailing list