RE: Subversion GUI client?

[snip]
The web site needs to have *a* working copy (or exported filesystem);
this doesn't mean that all developers must work in that same working
copy. Most people find this sort of setup very frustrating to use,
because it's impossible for one developer to isolate his changes from
the others'.

Also, any changes made to that one working copy affect *everyone* in
real-time. If one developer leaves a bug in his code and leaves for the
day, no one can get their work done until he fixes it.
[/snip]

1. Since Dreamweaver is their standard tool of choice as IDE, then let us remember that Dreamweaver is able to lock resources via .LCK files.

2. Isolating changes is not really sandbox-friendly, eh?! Obscurity is not really a good thing on ultra-high-priority web projects.

3. If a developer leaves a bug for another day... Then he should get fired. Employment security is taken for granted, and those who do not play nice in the sandbox deserve to get penalized for not doing their work (like documenting a bug for other people to see what is still buggy about their code). --> SVN does a great job in their bug tracking website at discussing what is in the works for each bug.

I have patience for people, but sometimes it's their own darn fault! :o)

Nasser Dassi
Sr. Technical Programmer
=========================================
E: ndassi@141xm.com
=========================================

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 26 20:20:41 2005