From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Joseph Huttner <jhuttner@appnexus.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git workflow for beta/production
Date: Mon, 14 Mar 2011 16:10:59 -0700 [thread overview]
Message-ID: <868vwh47ss.fsf@red.stonehenge.com> (raw)
In-Reply-To: <324BE2A8-5987-4324-AE27-D5CC01341710@appnexus.com> (Joseph Huttner's message of "Mon, 14 Mar 2011 15:27:22 -0700")
>>>>> "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
next prev parent reply other threads:[~2011-03-14 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 22:27 Git workflow for beta/production Joseph Huttner
2011-03-14 23:10 ` Randal L. Schwartz [this message]
2011-03-14 23:11 ` Junio C Hamano
2011-03-15 12:10 ` Drew Northup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868vwh47ss.fsf@red.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=jhuttner@appnexus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.