Page History

The JDK 9 project is experimenting with the idea of Submission Forests submission forests.  A Submission Forest submission forest allows committers to submit a change for automatic build, test and integration with an upstream forest.  Initially we have created a jdk9/hs-submit forest which integrates to jdk9/hs.  This will allow non-Oracle committers to make changes to jdk9/hs directly while still observing the Hotspot team's conventions for pre-integration build & test.  Of course all the usual rules about who may make changes and how they are reviewed and approved still apply.

Submission Forests forests are modeled after the JDK9 Sandbox Forest.  The default branch of the Submission Forest submission forest is kept in sync with its upstream forest.  Committers do their work on branches with one branch used per fix.  When a branch is pushed to the Submission Forestsubmission forest, it is automatically run through a pre-defined set of builds and tests.  If this succeeds, the changes on the branch are moved as a single changeset to the default branch of the upstream forest.  If a branch fails to build, pass tests or merge successfully into the upstream forest, no changes are made upstream.  At the end of the process a status email is sent to the committer.

The finer points of Submission Forests submission forests are covered in the FAQ below.  The jdk9/hs-submit forest will be maintained by <Duke>.  If you have problems, please send mail to <hs-xxx@openjdk.java.net>

...

When changes are pushed to a branch in a Submission Forestsubmission forest, a job is created on an internal Oracle system to build and test those changes.  Jobs which integrate to the same upstream forest are run sequentially in order to manage merge issues so it is possible that your job will wait for some time to get started.  Once running, a successful job should take about <60> minutes to complete.  Unsuccessful jobs will usually complete more quickly.  When your job is finished you will get an email describing what happened.  If you are subscribed to the change alias for the upstream forest, you should also see an email if your change successfully integrates upstream.

...