While I understand the sentiment of continuing to develop old lines
(branches) of code, that's just not viable. And this is something we have
all discussed as a (full) team a few times now. Once the next development
line is stable we stop developing the older line. That's even more true
within a release family - there is no need to continue to develop 5.x once
5.x+1 is stable. We do adjust that procedure slightly around major
releases, meaning that even after 6.0 is stable we continue to do those
5.x+1 releases *for a short time*
On Fri, Jan 5, 2018 at 7:06 AM 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".
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
>