The OpenJFX project maintains 2 main development repositories. We utilize the "Branching with Clones" method as described in A Guide to Branching in Mercurial by Steve Losh. The "master" repo is the one from which each weekly promoted build is made. You can think of it as the "golden master". The master repository must always be buildable. We never work directly against master. Instead, we have created different team repositories, and developers push their fixes into one of these team repositories. Each week, a team integrator will integrate from the team repository back into master. Thus, a bug fix that finds its way into a team repository will be integrated into master generally each week on Tuesday or Wednesday. Promoted builds from master are then produced and published, generally on Thursdays.At present we have only one team repository, the "8u-dev" repository. All teams work out of 8u-dev (graphics, web, scene graph, etc) so you will want to clone and work from graphics as well. The URLs for each of these repos has one "mainline" development repository on GitHub, the "jfx" repository. The URL for this repo is listed here:

• httphttps://hggithub.com/openjdk.java.net/openjfx/8u-dev/rt/jfx

Naming / History

The following is only for historical interest. For JDK 8 through JDK 10, including all update releases, we follow the JDK release numbers precisely. For OpenJFX 11 and later, JavaFX is no longer bundled, but matches the JDK numbering.

Releases of OpenJFX are based on street names or neighborhoods in San Francisco. This tradition started with JavaFX 1.1 and carries on to this day. The names we have used for releases past, present, and future are listed here.

Some have questioned, why bother with release names, why not just stick with numbers? Long story short, it is so that when release numbers change on us, we don't have to adjust everything in the project (such as tags in JIRA).

...