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

Re: Git workflow for beta/production

From
Randal L. Schwartz <merlyn@stonehenge.com>
Date
Mar 14, 2011, 23:10 UTC
Message-ID
<868vwh47ss.fsf@red.stonehenge.com>
In-Reply-To
<324BE2A8-5987-4324-AE27-D5CC01341710@appnexus.com>
>>>>> "Joseph" == Joseph Huttner <jhuttner@appnexus.com> writes:

Joseph> The catch is that after a feature has been stomped on in Beta, Joseph> it **may** go to Production, but only if Product Managers still Joseph> think it is an important feature. In other words, there is no Joseph> guarantee that a feature in Beta will ever make it to Joseph> Production. It may be axed completely, in which case it would Joseph> never get to Production and would be taken out of Beta. Also, Joseph> there is no guarantee that features that do make it to Joseph> Production will go in in the order that they went in to Beta.

Sounds like you want the same sort of workflow that git itself uses, with topic branches.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
Previous: Joseph HuttnerNext: Junio C Hamano
Message 2 of 4 in “Git workflow for beta/production”
  1. Joseph HuttnerMar 14, 2011
  2. Randal L. SchwartzMar 14, 2011
  3. Junio C HamanoMar 14, 2011
  4. Drew NorthupMar 15, 2011

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.