Quoting Tom Malia <tommalia@ttdsinc.com>:
> [Tom Malia] It's a team development is the issue. at any given time, I've
> got 2 or three programmers (non-in the same geographic area) working on the
> code for a single EXE. Some working on some features and bugs and others
> working on other features and bugs. In VSS, you don't have "merge"
> functionality so frequently one person checks the project out while other
> "get latest version" (the equivalent of export) and every works on the stuff
> they need to work in. Then, before you "check in" if you were one of the
> ones that just did an export, you Diff the entire project in your working
> folder against the current contents of the repo version of the project then
> go through and manually perform a merge and then check your stuff into the
> repo. I know this isn't the way things are "suppose to be done" but it's
> how things are done and it's really fairly functional for us for right now.
Maybe I'm missing some of the intrinsic details of the product you are
working on. Having one developer checking out the entire project and
by doing that locking everyone else out doesn't seem (to me)
appropriate _even_with_VSS_. No offense, but the fact that most of the
time everyone on the team minus one lucky guy has to work on unmanaged
files doesn't really sound very functional.
--
Jing Xue
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 19 18:43:01 2007