Re: Re: Re: Branching strategy - Feature vs Release

Hi Carlos,

> From: Dmitri Colebatch
> Sent: segunda-feira, 13 de novembro de 2006 18:55
>
> Here's how we work:
>
> 1. cut code, committing as frequently as possible without breaking the build, tests, or general functionality (on trunk)
> 2. create a tag
> 3. release tag to test for QA
> 4. if required branch off the tag to fix any bugs, retag (branch) and re-release to test. repeat as required
> 5. release QA'd tag to production

On 12/15/06, Carlos Alberto Leme Galassi <galassi@cpqd.com.br> wrote:
> When you said below "5. release QA'd tag to production" what exactly does it mean?
> Sent it back to merge in a trunk, or make a new tag?
> Could you explain me?

At step 2, we create a tag "tJunction_20061215a", build that and
release it to QA. At step 5 we build the same tag and release that to
prod.

cheers
dim

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 15 00:31:55 2006