[hibernate-dev] Plans to release 5.2.13?

[Steve Ebersole]

Certain parts of the release process are easy to automate, assuming nothing
goes wrong of course.  Other parts are not.  Which actually circles back to
some things I've been comtemplating about (ORM at least) releases.
Basically we have an elaborate set of steps we go through for a release
beyond just the "simple" aspects like tagging, building/uploading jars...
things like blog posts, forum announcements, announcement emails... and we
do these even for each bug fix release.  IMO we really should only be doing
some of these for a family (5.2, 5.3) initially going stable (Final).  I'd
love to see the release task (the actual Gradle tasks) do an announcement
when any release is performed - Gradle has an "announce" plugin that can
announce via twitter, etc.  To me that is enough for a generalized "hey
this new release it out" notifications.  The initial stable release of a
family (5.2.0.Final, 5.3.0.Final, 6.0..0.Final...) is special and the one
we should handle specially by doing some of  these other things.

But even on top of that stuff, its often just managing the backporting that
is resource intensive - identifying what should be backported and what
should not, not to mention managing the conflicts as we get further down
that path.




On Fri, Jan 5, 2018 at 7:16 AM Sanne Grinovero <sanne at hibernate.org> wrote:

> On 5 January 2018 at 13:05, Guillaume Smet <guillaume.smet at 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 at 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 at 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 at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>