Creating a branch is something the release manager does just before generating the first candidate for a feature release. For more context, see ReleasePrep
- To create a new branch, change directory to the root of your trunk code client and issue the following command, where $DOCS_ROOT is the root directory of your docs client:
ant "-Ddocs.root=$DOCS_ROOT" -quiet createBranch
Post a message to firstname.lastname@example.org requesting creation of a Hudson build job for the new branch.
After creating the branch, bump the version number on trunk. Again, from the root directory of your code client, issue the following command:
You will be prompted to enter a new release ID. Use 0 for the third and fourth numbers of the id and add "beta" to the end. This will guarantee that distributions built from the trunk will know that they are non-upgradable alpha versions. So for instance, "10.8.0.0 beta" would be a legal release id for the trunk.
- Also consider bumping the version number for the upgrade tests on trunk at this time. But this can also be done the next time new upgrade tests get added on trunk. You will need to do the following:
Add a new version number to DataDictionary.
Stuff that version number into softwareVersion at the beginning of DataDictionaryImpl.boot().
- Add a case for the new version number to DD_Version.majorToString().
- Add the new branch number to the list of branches on the source page of the website.
For instructions on how to build the website using Forrest, please see: http://db.apache.org/derby/papers/derby_web.html
The actual page to modify is src/documentation/content/xdocs/dev/derby_source.xml.