What I have had set up is a repo with branches. I am currently gearing up to implement SVN and we are also going with that model. Trunk is production and QA, Test have their own branches. Development uses project branches that are then merged into test, then qa, the trunk. Depending on their level of comfort, if you have a lot of people who are not used to SVN...just go with trunk being prod, test, qa, and dev all being common branches. That reduces a lot of merging. In all of these instances, the actual servers are all checked out of their respective branches.
Eric -----Original Message----- From: Scott Stewart [mailto:[email protected]] Sent: Thursday, December 29, 2011 2:16 PM To: cf-community Subject: Subversion, who's using it and.. What process do have set up: IE: is it just a base repository or are you taking advantage of branches and tags..? (I know this is pretty open-ended, but I'm getting ready to do an install of Subversion for about 20 developers, and I want to see how others are taking advantage of it) thanks sas -- -- Scott Stewart Adobe Certified Instructor, ColdFusion 8 & 9 Adobe Certified Expert, ColdFusion 8 & 9 Blog: http://www.sstwebworks.com Email: [email protected] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:345005 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm
