Which workflow(s) do you use?

[Bill Barry]

In our environment they all come from the main repo.

We put our releases into a separate repository and we tag the releases 
that get to production, but that is all:

our tiers are: dev -> qa -> demo -> test -> production
at any time, the main repo tip may be built and placed into the 
{project}-published repo
at this time,  qa gets updated from the latest revision in 
{project}-published
overnight or when no demos are scheduled and something major has 
happened demo gets updated from the latest revision in {project}-published
when it comes time to do releases, we tag the main repo and build into 
{project}-published
if all goes well in the qa environment, we replace the current contents 
of the {project}-stable repo with the tip contents of {project}-published
at this time, test gets updated from the latest revision in {project}-stable
during the next scheduled release, production gets updated to the latest 
revision in {project}-stable

Most of this happens automatically or via a single click in 
CruiseControl.NET

So, I suppose we keep separate repositories for environments (dev==main, 
qa/demo==published, test/prod==stable), but dev is the only one with 
source code.

bradford wrote:
> For those of you that do tiered web development:  dev -> qa -> staging
> -> production, do you all prefer to keep a separate repository or a
> separate named branch for each environment?
>