[cc'd back to the list -- please try to include the list in your reply,
helps other people find the discussion later]
Michael Armida wrote:
> Hi, Mike,
> Inline responses below.
>> How about checking out to the local drive for each workstation? Why
>> are the WCs on a shared network drive? If it's for backups, I'd
>> tongue-in-cheekly suggest your developers check in more often --
>> that's the wonderful thing about version control, you only have to
>> back up a central repository. I'm developing on a large, enterprise
>> project, and whilst we're not using Subversion everyone has a
>> personal WC on their own machine -- no network shares to worry about.
> We're a web development firm caught between a zillion different
> platforms and servers; because of the limitations of the non-server
> IIS and the general desirability to have all development on the same
> platform as is on the server, we run a Win 2003 server for our Cold
> Fusion sites. Thus, when we were previously working with CVS, we
> would simply run a checkout over a network drive onto that machine;
> the web server would then run one website per project per developer.
> Local checkouts would certainly be desirable, however, the problem is
> that absolute paths then have to be mapped back from the server to the
> workstation. The wonderful windows world of drive letters is
> restrictively small for (developers * projects) number of WCs.
Is it possible to have the Cold Fusion machine mount the developer
workstations and thus keep the working copies local? (i.e. have lots of
mounts *onto* the CF box).
>> Second question -- how often do you check out as opposed to updating?
>> Is update/status slow too? That's the more common operation.
> Fairly often, as there are about 15 different projects, and people
> constantly hopping between projects.
That kind of implies you're deleting your working copies -- can you
avoid deleting them? Disk space is cheap, right? Checkout is a big
operation, update much more efficient.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Mar 10 13:09:28 2004