I also agree with Jason and Cameron and I would think more than twice about this. Having your production code automatically in sync with the head revision of your repository negates the major benefits of version control.
The code that is being tested against should be committed into the repository *before* testing and approval (though of course it should be tested by the coder first). Here's a scenario off the top of my head: You write a new feature and it doesn't all pass QA because a designer changed their mind on how the thing should work; you go rewrite it the new way - they come back again and say they want it the original way after all: * Not versioned until now - you rewrite the code back again, possibly introducing a few bugs you didn't write the first time round... * Versioned at every step - click click click and you have reverted to the first revision Versioning gives you all sorts of freedom while you're *developing* code. Another example: say you want to try out an experimental feature; you could create a branch in your repository and code away to your hearts delight - commiting as you go. You finish your working prototype and everyone likes the new feature but you don't have time to polish it off and merge it back to trunk to push live - not a problem, its versioned and you can come back to it any time you like. Without ever commiting that code, you are stuck back in your pre-versioning dark days! Ok a little dramatic. I'm sure there are better examples than those but hopefully that helps illustrate the point. Dominic 2009/9/9 Jason Fisher <[email protected]> > > Totally agree with Cameron on this. One of the great benefits of version > control is that you can continue to monitor development changes while still > only pushing updates to production when the whole set of changes is ready > to go. I may have a set of changes that takes several days to code, for > example, but I don't want to go home each night with today's work living > *only* on my hard drive, so I commit to SVN every day (or several times per > day). That way, I get my backups and change history, but I can still > refrain from pushing to production until the new functionality is entirely > complete and tested. That's one of the core benefits of version control, > IMHO. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:326145 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
