Re: Subversion, TortoiseSVN, and Windows

I appreciate all the replies. This discussion has given me some major
insight into SCM and setting up development environments. Perhaps I
should also explain our current development environment in further
detail.

Our developers write code on their drives that are mapped to the C:\www
folder of the development machine. Development websites that reside on
this development machine are how and where the development code is
tested.

Once the development code is tested, it gets merged to C:\www of our
staging server, to which the developers also have mapped drives.
Staging websites that reside on this staging machine are how and where
the staging code is tested.

Once the staging code is tested, our project manager merges the code
into production.

Here is my current understanding of how we would use subversion:

Aside from having each developer run IIS and CF locally, which we don't
currently do (and are trying to avoid), our development machine will
have to do rather frequent updates of its own working copy, from the
repository, possibly using a tool like cruisecontrol. Each developer
will also have a working copy on their local machine that they
periodically commit to the repository.

It is not likely that we will do any branching.

Do I need to be concerned about everyone keeping their own working
copies consistently up to date?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 21 19:04:45 2004