RE: RE: Re: Suspending commits
From: Tjernstrom, Staffan <stjernstrom_at_mail.esignal.com>
Date: 2006-07-24 16:39:14 CEST
I have a couple of (more-or-less sensible) ways around on this one.
If you only ever submit a tagged build (we do about 2-3 a week), and set up your build environment to built from the tag (in reality just a branch), then there's nothing actually stopping you making a change under the tag that broke, then merging back into the trunk (as well as re-tagging the new (sub-)version of the tag.
Alternatively (and this is what we mostly do), is have a set of 'floating' branches, one of which is say called "Release Candidate", that you always build your release from. Each time to make a release, over-write the preivous branch with what you're releasing. This keeps the number of branches down to say 4 (trunk, in test, in UAT, in production). Essentially you're never in reality interested in what was in UAT 3 releases back.
Staffan Tjernström | Sr. Programmer - Market Data Systems | www.esignal.com <http://www.esignal.com>
From: Michael Pickard [mailto:email@example.com]
Because there may be a need to rebuild if something fails UAT, hence 'without my prior authorisation'.
If I needed to rebranch each time, I'd get at least one or two new branches a week *plus* any branches created by failed UAT - it would soon become unwieldy.
From: Mike Craig [mailto:Mike.Craig@freeclear.com]
Why not branch, and build from the branch?
Tel: +44 (0)20 7234 5857
Visit London is the official visitor organisation for London. Visit London is partly funded by Partnership, the Mayor's London Development Agency and the Association of London Government.
The information contained in this e-mail is confidential and intended for the named recipient(s) only. If you have received it in error, please notify the sender immediately and then delete the message. If you are not the intended recipient, you must not use, disclose, copy or distribute this email. The views expressed in this e-mail are those of the individual and not of Visit London. We reserve the right to read and monitor any email or attachment entering or leaving our systems without prior notice.
DISCLAIMER: This message (including any files transmitted with it) may contain confidential and / or proprietary information, is the property of Interactive Data Corporation and / or its subsidiaries and is directed only to the addressee(s). If you are not the designated recipient or have reason to believe you received this message in error, please delete this message from your system and notify the sender immediately. An unintended recipient's disclosure, copying, distribution or use of this message, or any attachments, is prohibited and may be unlawful.
This is an archived mail posted to the Subversion Users mailing list.