Best practice to control versions of software using SubVersion

In my repository the basic structure of one project is:

| project1 - Project Name
| web - Line of use / Web-HTTP)
| trunk
| tag
| batch - Line of use / Cron process
| trunk
| tag
| ws - Line of use / Web Service-Soap
| trunk
| tag

When is needed do one modification in Web Service per example, the
developer do checkout of "project1/ws/trunk" in one local directory
and do modifications to do task and after release commit. The
responsible for the project do update in your local directory,
analysis the modifications (changelog) and allow or deny it... if is
allow the modification are closed one tag with all modifications using
the command "svn copy project1/ws/trunk project1/ws/tag/releaseDay".

The problem: In my production server I have one checkout of the path
"project1/ws/tag/releaseDay" working so fine, but when is closed other
new release I need do checkout of new tag... And in some cases the
projects have a big size and this need be fast (in cases of
emergency)!

NOTE: "releaseDay" is variable, example: YYYYMMDDv

This process today works so fine and maintain in production server the
lasted stable releases to go back if anything not works.

Anyone has any suggestion to better this process and solve this problem?

Felipe Cardoso Martins
felipe.cardoso.martins_at_gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-18 23:28:41 CEST