On 7/24/06, Michael Pickard <mpickard@visitlondon.com> wrote:
> > You really ought to create tags and build from those. You'll get the
> > "lockdown" you're after (only allow one person to create tags), get a
> > "snapshot" of the code at any time as a result for repeatable builds,
> > and you don't have to stop developers from committing at all.
>
> OK, so let's say I create a tag and build for UAT from that.
> Dev A checks in some code,
> Dev B checks in some code,
> Dev A checks in some code,
> I'm notified of a failure in UAT and ask for a fix to be committed,
> Dev C checks in a fix
> I tag and build again.
>
> Isn't there a chance that the new build contains code submitted by A and
> B that may break an area of the codebase not covered by UAT ?
Yes, there is that chance. To avoid this, you can create a branch
from the version that was released to UAT, have Dev C code the changes
against that branch, then when UAT is finished merge the changes from
the branch into trunk.
If you get to having too many branches and/or tags, delete old ones.
They take up very, very little space in the repository to begin with,
so it won't be a waste of space.
Subversion offers so many ways to mange this requirement cleanly, I
can't imagine restricting checkins across the board for a day. I look
at my repository as not only source management, but a backup of my
work. Let's say, for argument's sake, that you lock out checkins for
UAT day. Dev A gets a good head of steam rolling today (Monday), and
makes a ton of code changes. But he's not allowed to check in until
Tuesday. His laptop gets stolen on the way home from work. Or his
hard drive crashes overnight. A full day's work - gone.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 24 14:42:52 2006