Appleton Brad-BRADAPP1 wrote:
> Clearcase can do this, by virtue of its virtual filesystem.
> I cant recall coming across a developer that ever preferred
> it to happen this way rather than having control over when
> their own sandbox (workspace) gets updated. Usually they
> just want notification to alert them when it happens.
I certainly prefer it this way; it's too easy to forget to
do the update before the checkin. The open source systems
that I use (CVS and Subversion) don't easily support
client-side pre-commit validation, though I'm sure someone
has done it somewhere. ClearCase, as you point out,
just makes it happen.
In a traditional code ownership approach, I consider
build-failures over concurrent check-ins to be a sign of
poor communication, poor design, or refusal to
refactor. Notifications, private sandboxes, etc. become
crutches to work around the fact that the interactions
weren't discussed in advance.
>>We've had this discussion before. The trick is to not be
>>disruptive. I suspect ALERTING someone that there was a
I find the alerting to be more disruptive than the changes,
because the alerts are asynchronous. This means I get a
notification that someone else has checked something in
when I'm in the middle of working on some problem. The
notification either disrupts my concentration, or I
ignore it - making it worthless. At least when I
find problems after doing an update and rebuild, it's at
a point in time when I'm actually prepared to do
something about it. With continuous updates, as in
ClearCase, normally the worst that happens is that a
build takes a bit longer since it has to recompile the
updated code as well as mine. If it does more, then
we're back to why neither of us knew that that would
happen.
Gary
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
