git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Tagging stable releases

From
Stefan Näwe <stefan.naewe+git@gmail.com>
Date
Apr 15, 2009, 16:15 UTC
Message-ID
<loom.20090415T161255-114@post.gmane.org>
In-Reply-To
<49E59BC9.5060906@op5.se>
Andreas Ericsson <ae <at> op5.se> writes:
Show 12 quoted lines
> 
> 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
Previous: Andreas EricssonNext: Andreas Ericsson
Message 3 of 5 in “Tagging stable releases”
  1. AsafApr 14, 2009
  2. Andreas EricssonApr 15, 2009
  3. Stefan NäweApr 15, 2009
  4. Andreas EricssonApr 15, 2009
  5. Tim MazidOct 28, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.