Branch Creation Procedure

These are the steps that need to be done for a Release Branch creation.

1. Branch and push the code base. Generally this is a branch from the existing master. The new branch should be named january_<major>_<minor>, for example january_2_0 for January 2.0. It is expected that january_2_0 branch will then be used to create 2.0.0, 2.0.1, etc releases.

2. Request protection of the newly created branch from webmaster on Bugzilla (this link will pre-populate the fields, just need to update branch name) See Bug 513497 for an example.

3. Create and run new CI job on https://ci.eclipse.org/january for the new branch.

   1. Sign-in and click New Job
   2. Set job name to january-<major>.<minor> to match the branch
   3. Choose Copy Existing Job and select most master branch job (or job of branch you branched from).
   4. Edit the new job to update references to specific branch. (in info, branch specifier and anywhere else)
   5. Save and run the job.
   6. Verify that job has published latest build to documented location on download.eclipse.org

4. Update JanuaryExamples.tpd to point at the new location on download.eclipse.org. (Note this should be further updated after RC and Releases are published so that the target platform of the branch's examples point at the appropriate build.)

5. Increment the version of the master branch.

   1. Use mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=2.2.0-SNAPSHOT -DupdateVersionRangeMatchingBounds=true so that further snapshots have a suitable version number.
   2. grep for the old version to make sure everywhere that was supposed to got updated. The two places that don't update properly are category.xml for source bundles and the reference to the target platform in the releng pom.xml.
   3. A suitable commit message is [releng] set version to 2.2.0-SNAPSHOT.