What's in the matrix is up to each project. You can remove content by
editing the .yml file for each series, and removing elements from site.yml
under projects.orm.integrations.
I'd argue that moving away from the matrix for ORM just because Java
compatibility is "not enough" will force us to add a special case just for
ORM, and I'm not particularly interested in doing that. But feel free to do
so, or to remove the compatibility matrix completely for ORM.
I think there could be more in that matrix than just Java though, like the
compatibility with various major RDBMSs, or with some connection pools. But
again, it's your call.
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
On 28 September 2017 at 14:30, Steve Ebersole <steve(a)hibernate.org> wrote:
Do y'all really think it makes sense to have JPA versions in this
ORM
"compatibility matrix"?
My concern is that it is more involved (as we then try to convey in the
section below that matrix) than a cell in a matrix/table with just a
version number.
If we end up treating JPA compatibility differently (removing from table)
then the table is just made up of "Java compatibility", which we can
probably illustrate simpler than a single vertical row of versions.
On Thu, Sep 28, 2017 at 6:37 AM Guillaume Smet <guillaume.smet(a)gmail.com>
wrote:
> On Thu, Sep 28, 2017 at 9:21 AM, Guillaume Smet <guillaume.smet(a)gmail.com
> >
> wrote:
>
> > I was talking about the ability to access the old series when they are
> not
> > displayed in the overview.
> >
> > AFAICS, this is definitely missing and we would need either a page with
> > all the series linked from the overview page or a button displaying the
> > retired series.
> >
>
> Done: I added a See older series button to the Releases / Overview page
> and
> to the Documentation page.
>
> --
> Guillaume
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>