As a reminder, OpenJFX 12 is now in Rampdown Phase One RDP1. [1]
During RDP1, the only restriction is that any enhancements will need
explicit approval to go in, although most enhancements should be
retargeted to openjfx13 now. Note that these restrictions apply to the
jfx-dev/rt mainline (and by extension, the develop branch of the GitHub
sandbox), since we have not yet forked a stabilization branch -- for
this release that will happen closer to RDP2.
We will use the same rules for RDP1 that the JDK uses [2], with the same
three modifications we did for the previous release:
1. Approval is needed from one of the OpenJFX project leads (not the
OpenJDK project lead)
2. Since we are not part of the JDK, we need to use labels that do not
collide with the JDK 12 release. As an obvious choice, derived from the
JBS fix version, we will use "openjfx12-enhancement-request",
"openjfx12-enhancement-yes", "openjfx12-enhancement-no" and
"openjfx12-enhancement-nmi" as corresponding labels.
3. No explicit approval is needed to push P4 bugs during RDP1, as long
as those bugs have otherwise met the usual code review criteria. Having
said that, I do not expect reviewers or developers to spend much time on
P4 bugs. We have less than 4 weeks until RDP2 and we would be better
served fixing higher priority bugs (doc bugs and test bugs of any
priority are fine to fix during this time).
Let me know if there are any questions.
-- Kevin
[1]
https://mail.openjdk.java.net/pipermail/openjfx-dev/2018-October/022761.html
[2] http://openjdk.java.net/jeps/3
