If it's a matter of reviewing code, I'm happy to help. In that case, my
name should be added as a reviewer.
BTW, I forget to check all the various ways I can be contacted, so a
personal email or hipchat message. helps.
On Tue, Jan 30, 2018 at 5:52 AM, Sanne Grinovero <sanne(a)hibernate.org>
In some cases - maybe not these specifically - I know people ask
review when it gets tricky, as you're the most thorough reviewer and
have deep knowledge of most areas :) Maybe that was the case, maybe
not. Good to clarify either way.
On 30 January 2018 at 00:59, Gail Badner <gbadner(a)redhat.com> wrote:
> I've seen at least one jira comment asking if I approve backporting to
> 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
> don't fall through the cracks.
> On Thu, Jan 25, 2018 at 9:51 AM, Steve Ebersole <steve(a)hibernate.org>
>> 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
>>> being the last 5.2 release.
>>> >From an earlier thread, it sounds like there is concern outside the
>>> 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
>>> master to 5.2 when the bugs apply to master. Is there more discussion
>>> done about this?
>>> FWIW, backporting to active community branches is everyone's
>>> responsibility, not mine alone.
>>> hibernate-dev mailing list
> hibernate-dev mailing list