[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SVN Structure/advantages

From: Fernando Freitas <nandows_at_gmail.com>
Date: Fri, 18 Feb 2011 12:51:36 -0200

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?

Thank you and best regards,

Fernando Freitas
Received on 2011-02-18 15:52:19 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.