Re: Git workflow for beta/production

quoted

quoted

quoted

quoted

"Joseph" == Joseph Huttner [off-list ref] 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
[off-list ref] <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion