> Hello, > I was working with some projects web that had this struture: > follows below. > > - All projects was in three branches. One branch for bugs, one > branch for improvement and one branch for deploy . > > So, I migrate each folder of project to a new project and began to > use a TRUNK and tags as recommended at svn book. > > > Formerly, at my "deploy tool", I was only using a branch for > deploy; > > Now I use a tag for each project to deploy. > > At work, I had to do just one switch for all projects. > > Now I have to do a switch for each project to work. (the projects > has dependence). > > I am new at SVN, and a have a question about it: > > > 1) What the advantages of to use the best practices (trunk and > tags) as recommendded at svn book, if my work is more hard?
trunk/branches/tags is just a recommended way to organize your repository, it is by no means required. We use it for some projects and not for others. There is nothing wrong with your promotion type layout if that is what works best for you. I think the main advantage to the recommended layout comes with open source projects that use svn... since everyone will understand that layout and will have a very good idea what is what. but even with trunk / branches / tag... there is no specification of what is on trunk. Is that where stable/tested code is. Or is that where WIP code is? BOb
