Luiz Daniel Lapolla wrote:
>Hi,
>
>We are improving our development process. We have been using CVSNT over
>the last two years. All of our development goes directly on the mainline.
>At each milestone a branch is created and development keeps going on
>mainline.
>
>This process led us into several problems with QA, broken builds and
>concurrent development.
>
>We are considering the adoption of a branch-by-task model:
> - A new branch (across all files) is created for each Change Request,
>based on the last stable milestone.
> - All the development for one CR goes on it's own branch.
> - After N cicles of testing and bugfixing the branch is scheduled to be
>merged with it's baseline.
>
>
The Perforce folks have a few things to say about using SCM effectively:
http://www.knowledgestorm.com/collateral/WTP/50369_07499_07194_bestpractices.pdf
Branching too much is probably not that helpful -- their advice is to
branch late, and because of conflicting policy for two codelines. How
big is a CR?
Cheers,
Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 6 17:12:54 2004