Multiple Trunks instead of Single Trunk

We plan to have multiple trunks instead of single trunk. As the newer versions of the product are developed with some of the modules using new technology, integration with new 3rd party products, it is becoming difficult to keep the latest source code in single trunk. It is difficult to maintain single Makefiles to build both versions of product etc.    Since typically newer versions are developed with new features, change in technologies, I thought it would be good to have one trunk for each version and have release version branch off them when required.    Is there a different way to solve this issue? Is multiple trunks a good approach?    -- Thanks

Last updated 14 years ago

they're just directories, and trunk is just a name. By convention though there is usually one. If you have different versions of a project, those would be branches often:    /branches/v1  /branches/v2  etc.    Of course it's always up to you.