RE: Release/Branching best practices

Hi James,

This is how we do it.

We have a repo as below.

>Trunk

>Branches

>Versions

>1_0_0

>1_0_1

>Tags

>SuccessfulBuilds

>1_0_0

>1_0_0_1

>1_0_0_2

The main work is done on the Trunk. Then each month we make a Version
branch of the current months version, ( just the first three numbers,
the forth is determined by the CruiseControl machine ).

The code on this version branch is released to the test team and tested
and any bugs found are then fixed on that branch and released again.

Then when that code is released to live the changes made are merged back
to the Trunk and another branch is taken.

Indecently each time the Version branch builds successfully a Tag is
taken with the version number and a deployment script is created.

We are not finding it too burdensome, the only problem we have found is
when people make changes to the same code in both places without merging
as they go.

What are currently doing?

Best regards,

Ian

________________________________

From: James Oltmans [mailto:JOltmans@bolosystems.com]
Sent: 28 November 2007 00:55
To: users@subversion.tigris.org
Subject: Release/Branching best practices

Hello all,

Could someone point me in the right direction for finding best-practices
or software to manage releases? We are trying to use a monthly release
cycle and our current branch and merge management is becoming a bit
burdensome.

Thanks,
James

www.sucden.co.uk
Sucden (UK) Limited, 5 London Bridge Street, London SE1 9SG
Telephone +44 20 7940 9400
 
Registered in England no. 1095841
VAT registration no. GB 446 9061 33
Authorised and Regulated by the Financial Services Authority (FSA) and entered in the FSA register under no. 114239

This email, including any files transmitted with it, is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you are not the intended recipient of this message, please notify postmaster@sucden.co.uk immediately and delete it from your computer system.

We believe, but do not warrant, that this email and its attachments are virus-free, but you should check.

Sucden (UK) Ltd may monitor traffic data of both business and personal emails. By replying to this email, you consent to Sucden?s monitoring the content of any emails you send to or receive from Sucden. Sucden is not liable for any opinions expressed by the sender where this is a non-business email.
The contents of this e-mail do not constitute advice and should not be regarded as a recommendation to buy, sell or otherwise deal with any particular investment.
This message has been scanned for viruses by BlackSpider MailControl
Received on Wed Nov 28 10:35:17 2007