On 5/15/07, Robertson-Ravo, Neil (RX) <[EMAIL PROTECTED]> wrote: > Personally, I would still release them in staged/known releases than > haphazzard fix on the fly. > > You will find it's a much better process and easier to manage.
Agreed. And if you have an *EMERGENCY* bugfix, you can use SVN to generate a patchfile of just that change and directly apply it to production until the next real build is ready. That's a slippery slope that should only be reserved for emergencies since now your tagged release in SVN is out of sync with production.... unless you use release branches, apply the patch to the release branch, and redeploy from there. Anyone that's been following this thread, please read the Pragmatic Programmers' book Pragmatic Version Control with Subversion -- it's the best, simplest, cheapest overview of subversion for real development tasks. I didn't write it nor do I get any money for shilling it -- it's just the best way to learn the commonly accepted best practices -- then you can take their base and figure out your own methods. If I was shamelessly plugging something, I'd be plugging my CFUnited 2007 class where I'm teaching Subversion, Ant, and Selenium for those of you needing a practical approach to version control, build/deploy tools, and testing. -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:278153 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
