On Friday, December 31, 2004, at 6:02:26 PM, Steve Berczuk wrote:
>> No ... "Everyone" is somewhere else, both physically and mentally,
>> coding away. A failed build interrupts everyone, or everyone
>> implicated, at their desk. But the whole theory of your idea is that
>> they have moved on. No one is ready, no one is engaged in the build
>> process. It's a fire alarm.
> Are we talking about the "pre-checkin-automated test" or the post
> check-in automated test after everyone runs tests in their workspaces?
> Jason and I are talking about the later.
> Or are we talking about having integration tokens where one person
> checks in code, runs tests, etc? Which could work, but may lead to
> very slow rates of change...
> ???(I'm confused).
I was still talking about Jason's proposal to run the tests
automatically and not commit the stuff that doesn't build, bouncing
it back to the devs. Have I missed a turn somewhere?
Ron Jeffries
www.XProgramming.com
Computers are useless. They can only give you answers. -- Picasso
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/
