The way I've used SVN before is to make the trunk the "unstable" development and then branch off "stable" versions. Means you always have a latest stable branch you can maintain / apply patches, while the trunk forges ahead. Branch another version off the trunk when it has progressed, then work on making that branch stable.
It does mean fixes applied to the branch need to be re-integrated back to the trunk, but merging fixes from a stable branch to the development branch is better than the other way round... I've only worked in small teams with SVN though, nothing on this scale.. Otherwise a Unstable branch sounds like the closest alternate to what I'm used to .. so It would be : Option 1 for me. ----- Hark Solutions Limited. Registered office: Unit 2 Cropmead , Crewkerne, Somerset, UK, TA18 7HQ. Company registration number: 05293155. VAT number: 849 5393 75. www.harksolutions.co.uk. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Hark Solutions Ltd. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Checked by AVG - www.avg.com Version: 10.0.1424 / Virus Database: 2437/5186 - Release Date: 08/08/12
