views:

40

answers:

1

I'm very new to Kiln and FogBugz (just started today). I'm currently using SVN + ScrewTurnWiki + BugNet to do all this things (... yes I know, frustrating ehh?). My question goes around the lines of best practices for organizing products into Projects/Repositories/RepositoryGroups.

My products have multiple VS projects and assets. In my particular case I have very large distributed applications that have several projects as part of a solution. Till now I've been managing these things on 1 single SVN repository (actually 2, one for legacy code and another for new code). As you can imagine the thing has gotten to a point where SVN cannot merge branches without a ton of conflicts, then I have to spend a tremendous amount of time resolving conflicts. This is a link with a picture of the folder structure I have for 1 of these products.



I know a lot of people will say "Do whatever you like the most"... that's why this is not a regular answer. I would like to hear from other engineers with similarly large and complex applications something that has worked for them. Suggestions and recommendations are very welcome.

Thanks!

+1  A: 

The answer to this question was accepted here on Kiln Stackexchange.

asmois