tagging releases

[Matt Harbison]

On Thu, 11 Dec 2014 08:42:22 -0500, Harry . <voldermort at hotmail.com> wrote:

> My release process currently includes
>
> 1) Updating the release version number in manifest(s)
> 2) Tagging the release
>
> This results in two consecutive changesets which essentially say the  
> same thing:
>
> 1) Update manifest to 12.6
> 2) Tag 12.6
>
> How do others do this? Is there a better way which doesn't clutter the  
> change log?


I skip the (tracked) manifest altogether and just tag.  The build script  
then invokes a script that does various 'hg log -r . -T ...' calls to get  
the tag, short hash, etc and updates the manifest as a prebuild step.  The  
exact nature of the script depends on the platform (linux/os x vs Windows)  
and type of project (C++ with native IDE vs Java with ANT build).

I was less concerned about commit clutter than I was about removing a step  
that can be easily forgotten.  Since the build script lives in the repo,  
the result should be the same every time any given tagged version is built.

--Matt