RE: Development / Production / releases

Here's how I'd organize it...
 
/branches
    /subproject-a-prod
    /subproject-b-prod
    /subproject-c-prod
/tags
    /subproject-a-1.0
    /subproject-a-1.1
    /subproject-b-1.0
    /subproject-b-1.1
    /subproject-b-1.1.1
    /subproject-c-1.0
    /subproject-c-1.0.1
/trunk
    /subproject_a
    /subproject_b
    /subproject_c
 
I wouldn't keep releases in your repository because they don't really
change - you just keep getting more and more. If you don't have any
other place to keep them, then I guess it's fine; but I'd suggest
keeping them in a folder and deleting the old releases when you add the
new ones - this way, every commit into those directories will be a new
release and you can go back to certain versions by using the logs to
determine the appropriate revision. This will save a lot of space as you
get more and more releases.
 
As far as giving users a place to update their production releases, I'd
suggest you create a branch. Merge to the production branch for
releases. Honestly, the best thing is to have them switch to a new tag.
So, if you release A 1.1, tag it and have users do an svn switch to the
new tag. Tags are for releases, anyway, and they shouldn't have any need
for updates, since they are meant to be a single moment in time. Tagging
would be easier to manage; but either approach should work.
 
Michael

________________________________

From: Esteban Pizzini [mailto:esteban.pizzini@gmail.com]
Sent: Monday, September 26, 2005 4:58 PM
To: users@subversion.tigris.org
Subject: Development / Production / releases

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)