To: OpenJFX Developers
As a reminder, OpenJFX 11 is now in Rampdown Phase One RDP1. [1]
During RDP1, the only restriction is that any enhancements will need
explicit approval to go in. 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 at RDP2, which starts on Monday, Aug 6 (at
23:59 Pacific Daylight Time).
We will use the same rules for RDP1 that the JDK uses [2], with three
modifications:
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 11 release. As an obvious choice, derived from the
JBS fix version, we will use "openjfx11-enhancement-request",
"openjfx11-enhancement-yes", "openjfx11-enhancement-no" and
"openjfx11-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 4 weeks until RDP2 and we would be better served fixing
higher priority bugs.
There are two "must fix" enhancements for this release that are in progress:
JDK-8205919: create artifacts and functionality to upload them to Maven
Central [3]
JDK-8195811: Support FX Swing interop using public API [4]
Other high-priority enhancements might be considered during RDP1, but
the closer we get to the end of the release, the more careful we will be
about including anything that introduces risk.
Let me know if there are any questions.
-- Kevin
[1] http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-July/022083.html
[2] http://openjdk.java.net/jeps/3
[3] https://bugs.openjdk.java.net/browse/JDK-8205919
[4] https://bugs.openjdk.java.net/browse/JDK-8195811
