svn - Is a good idea to put all projects in the same trunk? -
We understand the default and usually suggested svn repository organization, in case of many projects, there is something like this:
Many projects in our projects There is mutual dependence, and it will demand excessive use of svn: externals between them, we will use the D LL do not, we would prefer to see their source code instead of working with binary.
While splitting the repository branches, while syncing changes, there can be a complex and error-prone experience, so teams do not believe this solution at all.
A team member gave some suggestions which all of us think it might be a better solution: Put all the projects in the same trunk.
First of all, we have identified some problems from this point of view, but we all agree with these problems. I am based on hypothetical situations that we probably will never experience.
Can you see some serious problems with this solution?
We do this on our company and have great success.
We have three top level directories:
- Tags
- Branches
- Trunk
And then we have each project as a sub-director.
We still branch at the project level and still use svn: externals. But if we have a small source tree then we will do branches at the trunk level and will not use SVN: Extensions.
It is good to have the trunk of all projects in one place. You can return it, you can check it out and you have all the latest stuff together. You do not want to lose a single place for all branches nor have one place for all the tags because they are in the subdirectory of all / branches / Project X and / tags / Project X
Problems with svn: External:
If your projects are not excessive then you can divide the whole trunk to the branch every time and avoid all problems with svn: externals.
Problems with svn: The external is that when you make a branch, it does not automatically make you a branch for each SVN: externals. This is a problem because after all time your old branches will not be able to compile because your trunk will be further updated. Another problem is that if you fix a SVN in a branch, in the external, then all your other branches are broken.
Another problem with the SDN external is that when you log on to an SVN: root level, you do not see any change from the SVN external
Hope that a The day will be decided to remove the above problems of SNV, but till that day branches and SVN: External is a complete nightmare.
Comments
Post a Comment