Notes, rules and recipes related to Sirius release engineering.
Promoting a Milestone or Release
The jobs on our HIPP only publish "nightly" builds (using the script in
releng/org.eclipse.sirius.releng/publish-nightly.sh), which end up in
/home/data/httpd/download.eclipse.org/sirius/updates/nightly under names like
1.0.0-N20140605-075527. Promotion of such a build as a milestone is currently a manual (but trivial) process:
- Login on
build.eclipse.orgusing your Eclipse commiter credentials:
- Go into the root folder for Sirius update sites:
- Simply copy the whole update-site you want to promote from
milestones, under the final name. For example:
cp -a nightly/1.0.0-N20140605-075527 milestones/1.0.0rc4
- Optionally, copy the basic
index.htmlfile at the root of the milestone so that users who go to e.g.
http://download.eclipse.org/sirius/updates/milestones/1.0.0M6/instead of the platform-specific repo URL (
.../1.0.0M6/luna/for example) get pointers to the URLs they are looking for instead of a "Not Found" error message:
cp milestones/1.0.0M6/index.html milestones/1.0.0rc4
- Update the list of available update sites on the wiki to mention the where the
milestoneswill be published.
Promoting a release follows the same principles, except that it goes from
releases. Nothing should be promoted as a final release that has not been promoted first as a milestone (preferably with a "release candidate" status), and thouroughly tested.
Also remember that this recipe only deals with the "copying the bytes" parts of the process: an actual release involves much more than that!
Cutting a maintenance branch
There are several steps needed to create a new maintenance branch for a release. Assuming
master is at version 1.0.0, which is released, and that the next version will be 2.0.0, we must:
- Create a new Git branch named
v1.0.x, starting from the exact commit containing the final released 1.0.0 version:
git branch v1.0.0x v1.0.0(assuming the tag for
v1.0.0has been created).
- In the new
v1.0.x, bump the version number to 1.0.1 to be ready for the next service release on that branch.
- On the Sirius HIPP, create a new job named
sirius-1.0.x, starting from a copy of
sirius-master. Adjust the job description and the name of the branch to build. Normally that is all that is needed, the publication script knows were to publish the build if the version bump was done correctly.
- On the
masterbranch, bump the version number to the next planned version, e.g. 2.0.0.
- Update the list of available update sites on the wiki to mention the where the nightlies for the maintenance branch will be published.
- Announce the new branch and update-site on the
To bump the Sirius version, for example from 1.0.0 to 2.0.0, most of the changes required can be performed automatically. From a clean state, issue the following commands:
git grep -l "1\.0\.0" -- '*.xml' '**/*.xml' '**/MANIFEST.MF' '**/about.ini' | grep -v plugin.xml | while read f; do sed -i -e 's/1\.0\.0/2.0.0/g' $f; done sed -i -e 's/VERSION="1\.0\.0"/VERSION="2.0.0"/' releng/org.eclipse.sirius.releng/publish-nightly.sh
This changes the version number in all
MANIFEST.MF, and in the publication script. It excludes the
plugin.xml files because they contain the metamodel URIs, which should only change if the metamodel change in incompatible ways (and even then, in practice we don't change these and rely on our migration framework). Obviously this assumes nothing else than Sirius in the whole code base is using "1.0.0" as a version number, so carefully review the patch before commiting it (e.g. visually review the output of
NOTE: The instructions above will blindly update all the versions of all the exported packages, not just the bundles. In practice even if many packages of a given bundle break APIs in the next version, most will probably not. It would be better to follow precise semantic versionning rules (but as of this writing we have not setup anything to do this automatically).
Check the result builds correctly with:
mvn clean package
and check in
packaging/org.eclipse.sirius.update/target/repository that all features and plug-ins have the correction version.
See if any reference was forgotten with
git grep -l "1\.0\.0"
It is normal to have references to the old version in
@since annotations in the Java code, in the metamodels nsURIs, and in the release notes.
Once you are confident in the result, commit (and then push) using a message of this form:
git commit -s -m "[version] Bump version to 2.0.0"