...
Submission forests are modeled after the JDK9 sandbox forest. The default branch of the submission forest is automatically sync'd with its upstream forest. Committers do their work on named branches with one branch used per fix. When a branch is pushed to the submission forest, it is automatically run through a predefined 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 are covered in the FAQ below.
FAQ
| Table of Contents | ||||
|---|---|---|---|---|
|
...
A Simple Example
Say you need to make a simple fix to the hotspot README file in order to fix bug JDK-7000001. The following would do it:
| Code Block | ||
|---|---|---|
| ||
$ hg tclone --branch default http://hg.openjdk.java.net/jdk9/hs-submit $ hg -R hs-submit tdefpath -du <OpenJDK id> $ cd hs-submit/hotspot $ hg branch "JDK-7000001" $ echo "Make the README longer." >> README $ hg commit $ # Get your code review here $ hg push --new-branch |
FAQ
| Table of Contents | ||||
|---|---|---|---|---|
|
What should I call my branch?
...
Overview
Content Tools
ThemeBuilder