On 5 April 2018 at 22:03, Steve Ebersole <steve(a)hibernate.org> wrote:
I am assuming that mean you behavioral compatibility (they act the
same)...
Well that's the point of tests. The real problem is that often there are
not tests for a specific thing or someone changed the test expectations
during development
Agreed on the point of tests. But I'm wondering if we want to track
existing behavioural incompatibilities we know of in a similar
document / as an appendix of it / labels on JIRA.
Granted the binary compatibility is the first and most important
milestone, but I'd hope we could work also on some of the other ones
such as HHH-12454.
I'm not suggesting that we solve them all - but it would be good to
collect a list of known compatibility issues to review once more as
when we decided on breaking some thing we weren't evaluating problems
in the light of continuous delivery requirements.
Thanks,
Sanne
On Thu, Apr 5, 2018 at 3:56 PM Sanne Grinovero <sanne(a)hibernate.org> wrote:
>
> This report is focusing on binary compatibility. Which is great, but
> we should also pay attention to some other significant
> incompatibilities such as HHH-12454.
>
> How do you prefer to track those, if at all?
>
> David mentioned that we're only *required* to provide binary
> compatibility, but we could of course be a bit better than the minimum
> required - when doable.
>
>
> On 5 April 2018 at 21:48, Gail Badner <gbadner(a)redhat.com> wrote:
> > I basically re-ran the same report on the newer snapshots.
> > Incompatibilities listed in the old report that were resolved do not
> > appear
> > in the new report.
> >
> > I also categorized the incompatibilities as discussed in comments in the
> > second report (e.g., Failures Mitigated using Compatibility
> > Transformer).
> >
> > I un-crossed-out the issues that were not resolved yet (e.g., by
> > HHH-12424
> >
> >
<
https://www.google.com/url?q=https://hibernate.atlassian.net/browse/HHH-1...
> > ).
> >
> > I think the only unresolved comment was the one about
> > JPA_METAMODEL_POPULATION, so I responded to it in the new report.
> >
> > On Wed, Apr 4, 2018 at 3:53 PM, Steve Ebersole <steve(a)hibernate.org>
> > wrote:
> >
> >> Are these in addition to the original documentation? How do we
> >> correlate
> >> things from this new doc that have already been addressed via the
> >> previous?
> >>
> >> On Tue, Apr 3, 2018 at 8:00 PM Gail Badner <gbadner(a)redhat.com>
wrote:
> >>
> >>> I've re-run the report to see what is still outstanding.
> >>>
> >>> Here's the link:
> >>>
https://docs.google.com/document/d/1ZjdVuNzYPjjmvVd7mDLw9zwy9c0By
> >>> _FP0oj8DkHgiBE/edit?usp=sharing
> >>>
> >>> I'll share to the same people as the last report.
> >>>
> >>> Regards,
> >>> Gail
> >>> _______________________________________________
> >>> hibernate-dev mailing list
> >>> hibernate-dev(a)lists.jboss.org
> >>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>>
> >>
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/hibernate-dev