Re: Promotion

> Is there a way to have a promotion model using SubVersion?
> In a particular project we need to take state changes and not content changes.

I've been working with a setup like this:

/project/stages
           /development
                  /issue0
                 /issue1
                /...
          /testing
                 /issue2
                /issue3
               /...
        /closed
       /released
          

/project/environments
             /integration
            /preproduction

/project/releases/
           /20050101
          /20050203
         /....

each development is made in a branch inside the development stage.
Once it's finished, we move the branch to /testing and merge its changes
into /integration.
Once the testing is done and passed, we move it to /closed waiting for the
release.
When the release date is near, we merge into /preproduction all branches
that are intended to go in that release.
Once the release is tested from /preproduction, we copy preproduction to
be a new release.

Maybe messy, but we have a huge grade of paralelism in our developments, and
we don't always know if a given issue should be released or not, or when it
will be released...

_
Jorge

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 28 19:14:48 2005