-
Reserved checkouts can be very counter-productive. If two persons
want to edit different parts of a file, there may be no reason to
prevent either of them from doing so.
-
The experience of many
groups with unreserved checkouts is that conflicts
occur rarely and usually are relatively
straightforward to resolve.
Conflicts occur when two developers disagree on the proper design
for a given section of code; such a disagreement suggests that the team
has not been communicating properly.
-
With reserved checkouts it is common
to take out a lock on a file, planning to edit it, but
then forget to release the lock.
|
-
It is in general better to avoid
conflicts instead of allowing them
and afterwards resolving them again.
-
Unreserved checkouts are inappropriate if no
merge tool exists for the kind of file you are managing, for example
word processor files or files edited by Computer Aided Design
programs.
|