| commit | b41ddb31f5fc7ab356bc48e399309665ba2bc56d | |
| author | Thomas Leonard <talex5@gmail.com> | |
| Sat, 17 Nov 2007 16:28:00 +0000 (17 16:28 +0000) | ||
| committer | Thomas Leonard <talex5@gmail.com> | |
| Sat, 17 Nov 2007 19:54:57 +0000 (17 19:54 +0000) | ||
| tree | 084a12d835771c81b2eb76ca312bbea2b41dd874 | treesnapshot (tar.gz zip) |
| parent | 5c6f5e2cf36794dee4256e57ec217010ad277fe9 | commitdiff |
Added 'commit-release' hook.
If your local interface, you can define a section with extra release actions, like this:
<release:management xmlns:release='http://zero-install.sourceforge.net/2007/namespaces/0release'>
<!-- Update the copy of the version number stored in hello.py -->
<release:action phase='commit-release'>sed -i "s/^version='.*'$/version='$RELEASE_VERSION'/" hello.py</release:action>
</release:management>
Actions in the 'commit-release' phase are executed just before committing to the SCM the revision that will be tagged as
the actual release.
If your local interface, you can define a section with extra release actions, like this:
<release:management xmlns:release='http://zero-install.sourceforge.net/2007/namespaces/0release'>
<!-- Update the copy of the version number stored in hello.py -->
<release:action phase='commit-release'>sed -i "s/^version='.*'$/version='$RELEASE_VERSION'/" hello.py</release:action>
</release:management>
Actions in the 'commit-release' phase are executed just before committing to the SCM the revision that will be tagged as
the actual release.
| release.py | diffblobblamehistory |