RFD: Draft guidelines for working on jdk8u

Aleksey Shipilev shade at redhat.com
Fri Feb 8 14:41:30 UTC 2019

On 2/8/19 3:29 PM, Andrew Haley wrote:
> On 2/8/19 2:26 PM, Aleksey Shipilev wrote:
>> Changing the process to jdk8u-fix-requests would be a nice addition, from both backporter and
>> maintainer perspective. It also allows to manage and track backporting work [1][2] without going
>> certifiably insane.
> Please be precise about exactly what you mean by "Changing the process
> to jdk8u-fix-requests". Is it simply that we have to have one
> maintainer ack and appropriate fix requests in the database. If I'm
> going to write this up I have to know.

I would prefer to copy 11/12u process to 8u:

In that process, the "maintainer ack" is setting "jdkX-fix-yes" in relevant JIRA issue there. Once
you get that on the JIRA issue, you are good to push. When, how, and what issues actually get the
"jdkX-fix-yes" tag is solely at maintainers' discretion.

This would be an improvement over the current need to send the RFA to jdk8u-dev for every little
patch, every time copypasting lots of bug metadata that is already present in the bug tracker.


More information about the jdk8u-dev mailing list