Thanks Steve!
that's extremely useful.
My only doubt is the relation between release families, quoting:
>> Hibernate considers the {major}.{minor} combination a release "family".
and then later below in paragraph "The rules" :
>> API contracts should be considered stable across all releases in a family.
I'm not sure if you mean that 4.4.0 and 4.4.1 are (promised to be) API
compatible, while 4.3.0 and 4.4.0 are not..
I would say from the definition above that I should not expect that as
the two are in a different family, still the following example seems
to point out that any 4.x will be drop-in compatible with 4.0.0 ?
It would also help to understand the rules better to explain when the
team decides to bump the major version.
Sanne
On 9 August 2014 15:55, Steve Ebersole <st...@hibernate.org> wrote:
> There was a discussion in regards to our view on backwards compatibility in
> reference to HHH-9316. I realized that we talk about this amongst
> ourselves, but that I have never written these down. So I did that:
>
> https://github.com/hibernate/hibernate-orm/wiki/Compatibility-Considerations
>
> This is a first draft. Let me know what you think.
> _______________________________________________
> 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
