OpenJDK6 Release Process
Much of this information comes from Joe Darcy's informal notes
with edits from Lana Steuck.
Sources are kept in Mercurial repositories at:
Mercurial tags are used to mark the state of each repository with a
name jdk6-bNN where NN is a 2 or 3
digit build number.
Once the process is final, source bundles will be made available
The following steps represent the current process that should be
followed prior to tagging the repositories.
NOTE: Some steps may be done in parallel.
Send out email to "jdk6-dev at openjdk.java.net"
requesting any additional changes for this release
and announcing the start of the release process.
Perform full build and test on Linux, e.g. make all && make test.
Resolve test failures and repeat as necessary.
Recommended: Perform same full build and test for all
supported platforms and architectures.
Leverage any available Build and Test systems.
Recommended: Run TCK tests.
Posting results is limited to saying:
"all the tests pass so the build in question is Java(TM) compatible."
Request that formal builds be done by Oracle Release
Engineering as a verification, but also to have the
official source bundles created and posted.
Tag all the OpenJDK6 repositories and push those changesets
into the public repositories as soon as the source bundles
from Release Engineering are publicly posted.
The tags can be created with the following command:
sh ./make/scripts/hgforest.sh tag -f jdk6-bNN
Generate a Change Summary page.
Send out official email
to "jdk6-dev at openjdk.java.net"
on this OpenJDK6 release, including test results,
source bundle location, and the Change Summary page.
Post a blog entry
summarizing all release information.