best use formulating overthrow repositories?


our organisation (5-10 developers) skeleton adopt subversion the .net (visual studio) projects/solutions (visualsvn server, tortoisesvn / visualsvn).



what best proceed organize new repository tree? fine one large repository improved emanate different repositories each fortitude / product line etc.?



our projects categorized proceed (example):




  • main product line


    • main web app


      • library 1

      • library 2

      • ...


    • windows client

    • another windows fan

    • windows use


  • tools


    • tool a

    • tool b


  • product line 2


    • software 1

    • software 2


  • product line 3


    • app 1

    • app 2




Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?