tagging releases

[Arne Babenhauserheide]

Hi Harry,

My release process is:

- Update NEWS and autoconf.ac (version number) and commit that in
  default. Ensure that make distcheck works.  Commit message “prepare
  release x.y”

- merge to the stable branch, describe the changes in the merge commit
  (similar to the NEWS entry, but shorter - often just two or three
  keywords).

- tag and sign the merge commit (sign via gpg extension)

- merge the stable branch back to default and commit „merge stable
  into default“.

- push the changes.

Best wishes,
Arne


Am Donnerstag, 11. Dezember 2014, 13:42:22 schrieb Harry .:
> 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?
>  		 	   		  
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
> 

--
A man in the streets faces a knife.
Two policemen are there it once. They raise a sign:

    “Illegal Scene! Noone may watch this!”

The man gets robbed and stabbed and bleeds to death.
The police had to hold the sign.

…Welcome to Europe, citizen. Censorship is beautiful.

   ( http://draketo.de/stichwort/censorship )


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 299 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20141212/df42a8bc/attachment.asc>