Re: [hibernate-dev] Hibernate ORM 5.2 backports
I've seen at least one jira comment asking if I approve backporting to 5.2,
and I also remember seeing a PR that had "Requires Gail" label with a
comment suggesting bugfixes in older branches (including 5.2) must be
approved by me.
I just wanted to make this clear so that bugfixes that should be backported
don't fall through the cracks.
On Thu, Jan 25, 2018 at 9:51 AM, Steve Ebersole <steve(a)hibernate.org> wrote:
I don't think anyone mentioned expecting you to do this. In fact
the
discussions I have had about this was that others would help with this
(after 5.2.13).
On Wed, Jan 24, 2018 at 5:20 PM Gail Badner <gbadner(a)redhat.com> wrote:
> People seem to be relying on me to backport to 5.2. From a product
> standpoint, there is no need to backport to 5.2 anymore once 5.3.0 is
> released. Maybe 5.3.0 and 5.2.13 should be released together, with 5.2.13
> being the last 5.2 release.
>
> >From an earlier thread, it sounds like there is concern outside the ORM
> team that we need to keep 5.2.x releases going for some time.
>
> What is the criteria for backporting?
>
> Steve, Andrea, and I had a brief discussion about backporting bugfixes
> from
> master to 5.2 when the bugs apply to master. Is there more discussion to
> be
> done about this?
>
> FWIW, backporting to active community branches is everyone's
> responsibility, not mine alone.
>
> Regards,
> Gail
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>