No, this is not the best solution. It is the worst solution. All developers should be working in the trunk, when they finish their side project they then commit/merge that into the trunk. When you are ready to test/qa/release then you branch it off so it becomes the snapshot of what will be released.
Any bugs that are found that need fixing during this phase, should then be committed to that branch and then merged back into the trunk. Once the QA/Test phase is ready for release you then tag this branch, and delete the branch. There is a very good book out there, if you want when I get to work I'll post the name of it and it describes this process in greater detail. -----Original Message----- From: Jeff Gladnick [mailto:[email protected]] Sent: Friday, 7 May 2010 2:35 AM To: cf-talk Subject: How are other developers handling big SVN repositories? We have about 8 or 9 engineers and QA people working on a big cf application, all stored in SVN. The way we currently handle source control is at the outset of each mini-project, then one or two developers will branch the svn and work on that until they're done, then QA will merge the changes back into the trunk. The problem has become, we now have like 30+ branches, about 8 of which are used regularly, and QA is getting into merge hell. So....How do other developers handle svn with large projects and multiple people? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:333446 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
