Re: code promotion / changeset deployment process - best practices?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 15, 2005, at 7:23 AM, ed.wittmann@fiserv.com wrote:

> if I have this model:
>
> trunk ->
> ------------ testing ->
> --------------------development ->
> ------------------------------------developer-branch1
> ------------------------------------developer-branch2
>
> And my process is given as thus:
>
> - developer-created branches can only be merged with the development
> branch;
> - revisions to the development branch are merged with the testing
> branch
> for pre-release testing;
> - only revisions to the testing branch will be merged with the
> production
> trunk;

Branching is good, but too much branching is not gooder. :-)

I'd recommend this:

trunk
branches
   issues
     issue(id)
   maintenance
     maint(id)
tags
   trunk(id)
   maint(id)

Developers always work under branches/issues

Integration is done by merging from branches/issues/issue(id) to trunk
and/or branches/maintenance/maint(id) as appropriate.

Tags are made from trunk or branches/maintenance/maint(id) as
appropriate.

Testing is promoted to from tags only, no need for branches.

Production is promoted to from tags only, no need for branches.

- --
- -- Tom Mornini
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFCNxgBzaKkuvKwKvcRApUvAJ4mUzV13S2D4ZhuYz3CoHHa0me5xACcCInQ
EAK0WQi7ZcwGOZUI41a0K60=
=3o+J
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 15 18:19:40 2005