[Chandler-dev] How we develop post Preview : SVN topology

[Mikeal Rogers]

> s2. Multiple dev branches: maintain the trunk evergreen, devs  
> develop on their own branch and merge onto the trunk once their  
> feature/change pass tests and scrutiny by the community. Note: used  
> on really big FLOSS projects (Linux) and by commercial projects  
> (considered as best practice under Perforce for instance).

I don't know of any project that does this with subversion. Managing  
a lot of branches is a real pain in subversion, now there are tools  
to help (svk, Combinator), but I don't know any projects that hold  
this policy and uses subversion, but maybe someone else can give an  
example.

-Mikeal