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
This process led us into several problems with QA, broken builds and
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.
We are concerned with CVSNT performance, since our smaller project has
15,000 files and our development team throughput is around 150 change
requests per month.Recently, I read about subversion cheap copies and I'm hopping it canhandle all those branches that we are willing to create.Does this branch politic affects subversion performance? How it can becompared with CVS? Does anyone had a similar experience?Thanks in advanceDaniel
Received on Thu Mar 4 22:55:24 2004
This is an archived mail posted to the Subversion Users