On 5 January 2018 at 13:05, Guillaume Smet <guillaume.smet(a)gmail.com> wrote:
Hi,
AFAICS there are 52 issues fixed for 5.2.13.
And there are a couple of PRs waiting for review AFAICS (which might be
ready to be integrated or not).
So I think it would be really beneficial to continue doing 5.2.x releases.
5.3 is not there yet. And once it's going to be released, we would still
need the integrators to support it (be it WildFly or Spring) before
considering it fully consumable by the end users. And probably some time to
get it field tested too before we can consider 5.2 as being more or less
"dead" and just say to the users "upgrade to 5.3".
+1 I'd love to see more regular OGM releases, and some benevolent
maintenance time on 5.2 for a while longer even after 5.3 is
available.
We're all willing to help with the release process, including automate
it more; if someone on the ORM team could volunteer brains for the
organizational work we can make sure it's quick and painless by
delegating the annoying labour to Jenkins.
Thanks,
Sanne
My 2 cents.
--
Guillaume
On Fri, Jan 5, 2018 at 12:53 PM, Steve Ebersole <steve(a)hibernate.org> wrote:
> We should definitely stop doing 5.2 releases once we release 5.3.
>
> Of course 5.3 is held up waiting for answers from a few people...
>
> On Thu, Jan 4, 2018, 7:29 PM Gail Badner <gbadner(a)redhat.com> wrote:
>
> > We discussed stopping 5.2 releases at the F2F, but I can't remember what
> > was decided.
> >
> > I see that there is a 5.2 branch. Should we be backporting to 5.2 branch?
> >
> > Thanks,
> > Gail
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev