On Wednesday, December 1, 2004, at 3:13:57 PM, xperroni wrote:
> The approach advogated by XP -- let everyone write to files and then
> solve conflicts at code releasing time -- seemed a good solution. In
> eXtreme Programming Installed there is a very interesting description
> of a code management policy, but it is admitedly a simplified
> explanation. What references (specific or not) you recommend on the
> subject of code management? Are there any commentaries or personal
> experience you'd want to share?
Does Source Safe allow two or more people to check out a file, and then
issue a notice when the second person saves it back? Or does it not have
that ability?
Ron Jeffries
www.XProgramming.com
If we're not shipping our software when it's ready,
it's poor business practice.
If we're not sure whether our software is ready,
it's poor software practice.
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/
