[hand with pencil]
Stuff For Sale
2004 Summer Tour
About
Blog
Class Stuff
Email Me
Events
Gallery
Home
In The Press
Newsletter
Services
Smalltalk
Veggie Van Gogh

Credits
© 2002,
Bytesmiths

[this is simply a banner and menu bar]

Please patronize sponsors of this page!

Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.

This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!

[ prev | top | next ]

Revision History Needs

(This is a slide show. You really won't get 
anything out of it unless you have a graphical web browser with graphics turned 
on.)

- Every change made by a developer must be undoable, all the way back to the first "accept" of an individual method.

- The latest "accept" of a changed method must be instantly available to other team members, and vice versa: "Hey Fred, I just fixed that problem you've been having in your window opening code, so load my edition of 'open'!"

- Changes made by one developer are not automatically propagated to other team members, unless they re-integrate, or explicitly request such changes.

- Any browser that displays a code unit should be capable of displaying all versions of that code unit. It is not acceptable to force developers to interrupt their work flow by jumping to a special browser that only deals with temporal aspects of code development.

- Any browser that allows you to select from among code unit versions must also be capable of showing the differences between any two of those versions.

[ prev | top | next ]