I have a question about the proper use of trunk and branches for my SVN projects. For my team project, we create 3 major releases each year, and sometimes a minor release or two in between. At any given time, we can have an active development in 2 or even 3 issues. We are engaged in development in industries with a structure like:
/branches/project1/2009.01
/ branches / project 1 / 2009.06
/ branches / project 1 / 2009.09
/ branches / project 1 / 2009.10
Today, when I am ready to create a branch for the next version, I merged the changes from the current branch into the trunk, and then create a new branch from the trunk. Then I manually update the latest dev branches with bug fixes in previous release branches by merging through the trunk. No development or commit is ever performed on the trunk (except for committing for merges). Now I wonder why I even need a trunk. What would be wrong with just creating the next release branch directly from the previous release branch and merging the error correction errors directly from one branch to another, as well. Can I just delete the project under the torso?
All of SVN's best practice recommendations seem to indicate the use of a trunk for development, but using separate branches for each version seems a lot easier to me, since we can work with two or three releases at the same time. Is there any technical problem with my use of SVN? Suggestions?
Thank!
source
share