Re: Tagging stable releases

Andreas Ericsson <ae <at> op5.se> writes:

At $dayjob, we have an update hook preventing tags without the "-beta$X"
suffix from being pushed unless it points to an already tagged commit,
so our workflow goes like this:
1 hack hack hack
2 beta-tag
3 buildbot builds beta package and sends it off to qa
4 qa responds with "ok to release"
5 we stable-tag the exact same version we shipped to qa
6 buildbot builds stable tag and copies it to "to-be-released" directory
7 release-manager pushes the release-button once changelogs and stuff
  are in place

You've been talking about using git at your $dayjob quite often.
Any chance to share some of your 'infrastructure' (like hooks, e.g.) ?

Thanks

Stefan