It all depends on what you deem "production code". You don't keep a seperate code branch per system do you? (dev, test etc) surely you have a single release build as part of your software cycle and that same build is on all of your servers apart from dev which will be that build + more?
You can also check out code without svn folders, but I am sure you know that. "This e-mail is from Reed Exhibitions (Gateway House, 28 The Quadrant, Richmond, Surrey, TW9 1DN, United Kingdom), a division of Reed Business, Registered in England, Number 678540. It contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender or call our switchboard on +44 (0) 20 89107910. The opinions expressed within this communication are not necessarily those expressed by Reed Exhibitions." Visit our website at http://www.reedexpo.com -----Original Message----- From: Andrew Scott To: CF-Talk Sent: Wed May 09 20:43:40 2007 Subject: Re: Adobe CS3 Web Edition leaves me wanting, moving to Eclipse! W AS (RE: Frameworks) Thats why tools like Beyond Compare is good, you only migrate the files or merge what has changed. But I still wouldn't modify code on production, or even SVN production code. the reason being is that you also end up with all the svn directories there as well. But hey if it works for you... I just frown upon the idea that you are doing it this way, and DO NOT consider what you do, to be best practice at all. On 5/10/07, Russ <[EMAIL PROTECTED]> wrote: > > > -----Original Message----- > > From: Andrew Scott [mailto:[EMAIL PROTECTED] > > Cool, > > > > Still curious why Russ trunks a production server... > > > > > > We have a fairly large codebase, and it takes a while to check it all out. > If I'm doing a small change (lets say a spelling change, etc). I can just > go into that folder and do an update and it will take only a second or > two. > Or I can even do an update of the whole source tree, and it will still not > take very long. > > I really don't see the point of exporting a whole fresh copy of the code > just for a simple change. Even for larger changes svn update would be > much > more efficient then exporting a new copy of the code. > We also use FRS to replicate the files between cluster members, and if I > were to export the whole code tree, it would have to sync every file to > the > other cluster members. > > Obviously developing straight on production is a no-no... but if there's > an > emergency, I can either roll back to an older revision, or fix the code in > place and then commit it straight from production. > > With all these benefits, I don't see why you wouldn't trunk to production. > > If you're talking about why we use trunk instead of a branch, that's just > a > decision we've made that works for us. Trunk is always the latest stable > code that's on production, and it makes making small changes easy. As I > mentioned, for larger changes we use branches which get merged into trunk > once they've passed QA. > > Russ > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:277522 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
