JavaFX 16 is in Rampdown Phase One (RDP1)
kevin.rushforth at oracle.com
Thu Jan 7 16:21:33 UTC 2021
JavaFX 16 is now in Rampdown Phase One (RDP1) . We have forked a new
jfx16 branch  for stabilizing the JavaFX 16 release.
Here is the short summary of what this means:
- The master branch of the jfx repo is available for integrating bug
fixes or enhancements for openjfx17. Most fixes will be integrated to
master for 17.
- The jfx16 branch of the jfx repo is now open for integrating fixes for
openjfx16 that meet the RDP1 criteria as outlined below.
- Reviewers and Committers now have an additional responsibility to
verify the target branch of each pull request.
- I will periodically sync jfx16 --> master, meaning that developers
should integrate fixes to one or the other, not both
P1-P3 bug fixes, and test or doc fixes of any priority are good
candidates for integrating to jfx16 during RDP1. The only hard
restriction is that enhancements need explicit approval, over and above
the review of the PR, to go into jfx16. The bar for such approval is
appropriately high. We also need to be careful to avoid potentially
risky fixes during this time. Note that these restrictions apply to the
jfx16 branch. The master branch is open for all openjfx17 fixes,
As a reminder, we are using a single openjdk/jfx GitHub repo with
stabilization branches  rather than creating separate stabilization
repos. The jfx16 branch is used to stabilize the upcoming openjfx16
release. Please be aware of this, especially if you are a Reviewer or
Committer in the Project. This allows all pull requests to be in the
same place, but care needs to be taken for any PR that is targeted to
jfx16 to ensure that it doesn't contain any commits from master after
the jfx16 fork date. What that means is that if you intend a PR to be
for jfx16, don't merge master into your local source branch!
IMPORTANT: Reviewers and Committers now have an extra responsibility to
double-check the target branch of each PR that they review, integrate,
or sponsor. By default a PR will be targeted to `master` which is the
main development line (OpenJFX 17 as of today). This is usually what we
want. A PR should be targeted to `jfx16` if, and only if, it is intended
for OpenJFX 16 and meets the criteria for the current rampdown phase
(we're in RDP1 as of today). Reviewers are advised to be extra cautious
in approving potentially risky fixes targeted to `jfx16`. If there is a
concern, then a reviewer can as part of the review indicate that the PR
should be retargeted to `master` for 17. Reviewers also need to be extra
careful when reviewing PRs targeted to jfx16 that it doesn't mistakenly
contain any commits from the master branch. You'll be able to tell
because the diffs will contain changes that are not part of the fix
being reviewed. Such a PR will either need to be closed and redone, or
it will need to be rebased and force-pushed.
We will use the same rules for RDP1 that the JDK uses , 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 16 release. As an obvious choice, derived from the
JBS fix version, we will use "openjfx16-enhancement-request",
"openjfx16-enhancement-yes", "openjfx16-enhancement-no" and
"openjfx16-enhancement-nmi" as corresponding labels.
3. No explicit approval (no JBS label) is needed to integrate P4 bugs to
the jfx16 branch during RDP1, as long as those bugs have otherwise met
the usual code review criteria. Having said that, most P4 bugs should
now go into master for openjfx17, since we do not want to risk anything
that would destabilize the openjfx16 release without a compelling
reason. Also, we have only 3 weeks until RDP2 of openjfx16 and we would
be better served fixing higher priority bugs. Note that doc bugs and
test bugs of any priority are fine to fix for openjfx16 during this time.
Let me know if there are any questions.
More information about the openjfx-dev