Definitely look into creating a tag and deploying to your production server from that tag rather than the head revision of your repo. If something breaks with the deploy, you can very easily re-deploy the tag immediately prior to your new one and be right back where you started in just a few minutes.
Also, for those shops that have releases to production only on certain days of the week, you can create the tag on Monday (for example) and continue coding even though that production push may not happen until later in the week, but not change the code that was approved on Monday to go to production. Having a shared dev or something similar tie into SVN with a post commit hook is something that we've done in the past, but never a production server because of the issues that the previous folks have commented on. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:326152 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
