Re: Is SVN ready for use?

"Roman Rytov" <rrytov@entopia.com> writes:

> What I don't know is how to enforce programmers to update and commit
> their changes on a regular basis.

How about wiping their hard disks at irregular intervals? That'd sure
teach them. :-)

Why aren't they updating and committing on a regular basis already?
Seriously, it should be something they do often and automatically, so
try to identify the reasons.

Perhaps having people work on branches (again, see the SVN book) would
help? It sounds like you perhaps need better project management.

> Now my team is working with VSS

When I used VSS, we often had breakage from partial
checkins/checkouts. This is something Subversion (and CVS) helps
alleviate, IME.

It is difficult and hard work to introduce a new tool; perhaps try to
get some of the more willing on a pilot project?

(Just some quick ideas -- good luck!)

-kzm

-- 
If I haven't seen further, it is by standing in the footprints of giants
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org