tagging releases

[Mads Kiilerich]

On 12/11/2014 02:42 PM, Harry . 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?

That's not clutter. That's just how it "has" to be when we want tagging 
be version controlled and also want to be able to do it after the fact. 
Just get used to it and embrace it. (See 
http://mercurial.selenic.com/wiki/TagDesign for details.)

(I do however think it would be nice to also have the option of other 
ways of naming changesets at commit time. Something like named branches, 
only not sticky. You can already used named branches instead of tags, 
but you will have to be very careful to deal with the stickyness of 
branch names.)

/Mads