The OpenFX 8u60 release is aimed at stabilization. The main theme will be fixing regressions introduced in 8u20 or 8u40, and other bug fixes as the opportunity arises. Minor API changes are possible once we firm up the scope of the release. No new features are planned for 8u60.
Development repo: http://hg.openjdk.java.net/openjfx/8u-dev/rt
NOTE: 8u-dev changes are no longer synced into 9-dev automatically. It is now the developers responsibility to push bug fixes directly into 9-dev and backport them into 8u-dev. This requires developers to have a separate repo for each of 9-dev and 8u-dev: You cannot switch between 8u-dev and 9-dev using a single repo! The typical way this is done is to export the changeset (or MQ patch) from your local 9-dev repo and import it to your local 8u-dev repo.
Rules for pushing code to 8u-dev
The 8u-dev repo is locked during the week of June 29 (at least through the RDP2 build). After this week, only release critical bugs can be fixed in 8u60, and only then with approval from the JDK release team.
We are approaching the end of 8u60 bug fixing. The following highlights the schedule and rules for the rest of the release:
Mon, May 25 – Sun, Jun 14: Standard code review policies in effect
Bug fixes are subject to the usual code review policies (pre-commit or post-commit review as appropriate); since we are already past RDP1 the focus should be on regressions and P1-P3 bugs.
If you are backporting a bug fix (no API changes) from 9-dev to 8u-dev that is substantially the same changeset – either it imports cleanly or only differs from the 9-dev patch in white-space or context -- then a separate review is not needed to push to 8u-dev. The review you did for 9-dev is enough. If the changeset patch imports cleanly, then all you need to do is build / test and then you can push it.
Mon, Jun 15 to Sun, Jun 21 – regressions and critical bugs only, pre-commit review required
All bug fixes require a pre-commit review; an exception is made for changesets that do not touch shipping code, such as fixes to unit tests and non-shipping examples/toys
Changes should go to 9-dev first (which may be done with either a pre-commit or post-commit review) and then backported to 8u-dev for 8u60 with a pre-commit review.
Mon, Jun 22 to Sun, Jun 28 – regressions and critical bugs only, tech lead approval required
All bug fixes require a pre-commit review and also a "+1" from the tech lead (Kevin); an exception is made for changesets that do not touch shipping code, such as fixes to unit tests and non-shipping examples/toys
Changes should go to 9-dev first (which may be done with either a pre-commit or post-commit review) and then backported to 8u-dev for 8u60 with a pre-commit review and approval.
After Mon, Jun 29 any changes require JDK release team approval.
Sanity Testing / Weekly Code Freeze
Weekly sanity testing is performed to catch errors early. During this time, the repo is "frozen". See Sanity Testing for details.