I've got a project that's using SVN for it's versioning system. The project
it's being used for is a website, whose code relies heavily upon a database
for searching & authentication. Presently, for this project, we've got the
standard "trunk/" and "branches/" directories, with only one directory under
the "branches/" directory, called "dev" (where we keep all of the development
changes).
When we first started using a revisioning system (starting with CVS, then
thankfully migrating to SVN), all of the development team worked on only one
project, which was usually a short one, and then merged changes from the
development branch ("branches/dev") into trunk. Now that we're working on
multiple large projects, I'm not so sure that the current scheme is going to
work.
Given all that information, my question is this: what is the best way, in
your experience(s), to determine what qualifies as needing it's own branch?
I was considering making a branch for each project, but that seems like a lot
of potential merging that might not be needed. Any and all comments will be
appreciated. Thanks.
- Dan Falconer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 24 16:44:06 2005