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

Development / Production / releases

From: Esteban Pizzini <esteban.pizzini_at_gmail.com>
Date: 2005-09-26 23:58:27 CEST

Hi List,

I've the following situation and I'd like to know some suggestions about how
to solve this:

I've the following structure in svn

Project:
---> devel
--> subproject_a
--> subproject_b
--> subproject_c
--> releases
----> subproject_a
--->release_1
--->release_2
----> subproject_b
--->release_1
----> subproject_c
--->release_1

I have some users that only have to "update" files for production use... so
today they have to update the last release for each subproject...
I'm looking for another structure where users only have to update from only
one folder (for instance, "production"), but I want to mantain the releases
too...
I was thinking about another structure like this:

---> devel
--> subproject_a
--> subproject_b
--> subproject_c

---> production
--> subproject_a
--> subproject_b
--> subproject_c

---> releases
--> production_01
--> production_02 (where production_xx contains all the subproject folders
for that release)..

What do you think about this???
Any other suggestion?? or best practice for this??

Thank you!!

--
----------------------------------------------------------------------
Esteban Pizzini
(http://mod-apache-snmp.sourceforge.net)
Received on Tue Sep 27 00:00:15 2005

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