On Fri, 2006-10-13 at 07:39, Phyrefly wrote:
> > Are you certain you want a shared dev environement? As a developer, I hate
> > to use shared environements because I'm never sure when a problem is due to
> > my change or something Bob changed. And I would never want my dev
> > environement, shared or not, to be automatically updated without knowing
> > when or what was updated.
>
> I have no choice, unfortunately. Because it's a web project (or more
> accurately collection of projects) - and management won't let us run
> IIS on our local machines, we need to put the changes on the dev
> server to see the result.
This isn't particularly related to subversion, but a better
way to handle this is to set up virtual servers for each
developer on your development server. There are any number
of ways to do this. One would be to tie the vhost to a
different port number and let the server map the developer's
shared directory - or the other way around. In any case you
really want different people to able to test different
changes at the same time - otherwise the need for a few
quick fixes to your current version will kill the schedule
for the next major change.
> So there will be people doing HTML/design
> work, then I'll pick it up and do the ASP bits, then give it back for
> them to neaten up the look and feel again.
You'll continue to have that problem though as long as you have
to touch the same pieces. Separating as much of the look as
possible into css can help.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 14 18:19:13 2006