Question

All –
I have read several posts here about svn repositories layout best practices and unfortunately none of them have helped me decide what route is best for us, so I would like to ask for your opinion on how you would structure a repository based on this information:

1. Moving forward most of our code will be developed in C# and be .NET applications.
2. Our previous web development was done in Java.
3. We have some REALLY old programs developed in Delphi that are not modified much and when we move to our new case management system all the Delphi applications will be obsolete.

Based on these bits of information would you have a single repository for all the different source code or have a repository for each type of source (ie one Delphi repository, one Java and one .NET)?

Remember, in a year or so all the Delphi code and a lot of the Java code will be obsolete. Which makes me think having them in separate repositories might be the best way to go since we won’t be needing to keep any of that code after our migration.

So, my question is basically would you have a single repository or 3 separate ones for each type of code?

Thanks!
Leslie

Answer 1

Actually the decision on what goes into one repository should depend on how these projects/ applications are related, not what language they are in. Stuff thats not related should not be in one repo.

As it is a migration you could have separate repos for the new stuff (.net) and the old stuff (java+delphi), if you really want to throw it away afterwards.

And as you wrote “applications” – maybe you should consider several repos for the new software!? Putting too much into one repository makes it less flexible. Depending on what your projects really are that could also mean that you end up with several differently mixed repositories…