RFD: Draft guidelines for working on jdk8u

Langer, Christoph christoph.langer at sap.com
Fri Feb 8 10:25:34 UTC 2019

Hi Andrew,

> > I'd like to propose that for trivial backports/changes (i.e.: typos,
> > copyright fixes, etc.), a jdk8u reviewer approval is enough to have the
> > patch in. In case that a reviewer is not sure about the triviality of a
> > backport/change, other reviewers or maintainer approval may be required.
> > This would reduce unnecessary overhead I believe.
> I'm not at all convinced that we need to use the double-review system. Once
> people are aware of the rules, any qualified jdk8u reviewer should be able
> to apply them.
> Having said that, we must tag the bugs chosen to be applied to 8u in the
> bug database. I don't think I mentioned that in my posting.

You mean that we install something like a "jdk8u-fix-request" labeling procedure where the maintainer will approve each fix by "jdk8u-fix-yes" before it can be pushed to 8u, no matter how trivial the fix is?
Essentially the same as we handle jdk11 and higher backports? I'd be very much for that...

Best regards

More information about the jdk8u-dev mailing list