While CF is not a compiled language, the old version control maxim "Don't Break the Build" still applies.
Commits should represent a logical unit of work, and shouldn't leave the app in a broken state. Version control is not meant as a backup system, or an uber undo function - it's intended as a means to retain a history of meaningful changes to an application's state. This is particularly important in a team environment, when other developers may update their working copy at any time. If a half completed set of changes is committed, then their updated working copy may now throw errors, which causes all sorts of issues and wasted time. It's important to think of it in terms of how a revision may be used in the future. If I need to pull a particular revision, I should be able to look at the history and see, via clear commit comments, what changes were made to create that revision, and be fairly confident that if I actually check out that revision that it will function. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:277747 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
