> -----Original Message-----
> From: Michael Feathers [mailto:[EMAIL PROTECTED]
> Sent: jeudi 30 d�cembre 2004 18:33
> To: [EMAIL PROTECTED]
> Subject: Re: [XP] Seen on Massol's blog: Unbreakable builds
>
[snip]
> The problem is... it cycles back on itself. In your system, developers
> don't have to care about committing frequently, they have to care about
> committing frequently and correctly. And, it appears that in the
> situation you outlined, they don't care about committing correctly yet.
Hey, good point :-) That said, in our current situation, I think it would
help the commit rate rather than the opposite.
There's a potential nice side effects with "unbreakable builds". Imagine I
am a developer that keep piling up work on my local machine without
committing. Say, the end of the iteration is close and I want to commit all
in a bunch. It is very likely that the build will fail because I have either
not updated my local workspace or I have made modifications to code that
breaks others. Thus it'll take some long time to now merge my changes and
I'll have to discuss with others to come to an agreement. I may have to fix
their code too as I have broken it. After a few times like this, it should
dawn on me that there is a better way to do it by more frequently
committing. Others will also point it.
But still we'll need a coach to help share the values of continuous
integration.
>
> In cases like these, teams are usually in a good deal of pain. The key
> thing is to get them to feel what it is like when good habits get them
> past the pain rather than applying analgesics.
Agreed.
Thanks
-Vincent
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/
