[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: branching/development strategy

From: Noel L Yap
Subject: Re: branching/development strategy
Date: Tue, 27 Mar 2001 16:08:17 -0400

Take a look at


address@hidden on 2001.03.26 22:36:36

To:   address@hidden
cc:   (bcc: Noel L Yap)
Subject:  branching/development strategy

I was hoping this would be discussed on this list but I haven't seen it yet.

When you have a project that you're working on for several customers, what
do you do for frequent releases?  When do you branch and merge?  I've
scanned the open source CVS book (
but I didn't find any specific mention of this topic.

What we have been doing is making a DEVELOPMENT and a PRODUCTION branch for
each customer as we near the alpha or beta stages.  The programmers check-in
only to the DEVELOPMENT branch and the integration request person merges
specific requests from the DEVELOPMENT branch to the PRODUCTION branch.
Individual releases are tagged on the PRODUCTION branch from the builds that
the customer receives.

Are there more effective ways of doing this?  Pointers to archives, web
sites, or dead trees are welcome.


Info-cvs mailing list

This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]