Single SVN repository or many? (Poll)
A few weeks ago I had a very interesting conversation with a colleague. The question was wether or not we should store multiple (derived) projects into a single repository, or should we have a single project per repository.
My personal favorite is the single project per repository, because I like the separation of projects, having (somehow) meaningful revision numbers and portability in sense of moving repositories around or backing them up.
But my colleague pointed out some pros for his preferred method: one repository for multiple derived projects. For example, you can more easily merge changes (made in different projects) back to the “base” project.
While googling for some best practises, I saw that the internet is pretty devided. Time for a poll for my fellow developers: what’s your personal preference?
Feel free to elaborate your answer in the comments below.
-
http://twitter.com/Gerard_vHelden Gerard van Helden
