JDK Updates Project Page

[Mario Torre]

On Thu, Nov 9, 2017 at 1:43 PM, Mario Torre <neugens at redhat.com> wrote:

> Right, I see what you mean. It makes sense to have exclusively at JBS
> based process. We will still need to ask for review via email, but I
> think having a template for that may be overkill. Do we expect emails
> on jdk-updates-dev to be anything but backport requests?

It now occurred to me that the process may be just done exclusively on
JBS, including the review process:

1. A developer wants to backport a fix from n+1 into n creates a
backport request (marking the bug backport-request or whatever)
2. The bug is updated with links to the new webrev and all the
information needed
3. The review happens on the bug tracking system. The Lead either
approves the backport request or ask the original reviewer for review.
4. If the request is approve, the bug can be backported
5. Repeat for each backport version (perhaps is worth to create
separate bugs for each backport)

Assuming that for 8 and 7 there is still the old process in place and
that there is just one update-dev at any given time (two with the
LTS), the process seems quite streamlined. It's not different than
what is  being proposed, just happens on the bug tracking system and
not on the mailing list, which is nice since it's easier to see the
reasoning behind each bug and recreate its history.

What do you think, would that be of any help?

Cheers,
Mario