svn - Has this branching strategy sense in a web development ecosystem? -
i don't know if question stack-overflow related or should posted on stack-exchange platform, anyway.. the problem new branching system have in mind adopt in near future. @ work develop primarly web applications (ecommerce, cms, classified, special purpose) , websites in php , our vcs svn . this new model want adopt: trunk : development staging (branch): branch created test new features on remote ambient (the same system live has, same server..) live (branch): branch live. other branches develop concurrent features. now, idea bugfix live , push changes trunk. develop features directly on trunk or branches merge trunk. push trunk staging ready new features go live soon; , then? how can staging live branch? have pass trunk? now strategy is: trunk : it's live version branch each feature live bugfix done trunk pushed branches staging working copy switchs branch @ end of development of feature, before merge trunk. but method has drawbacks: al...