Woodward, Gordon (RBC Dexia IS) wrote:
>> I guess not, because repositories by definition don't share any relation, so the two will be completely separated from each other. Just wondering, but > why do you even want separate repositories?
>
> It's more of a security issue raised by management. The reasoning behind the second repository is to more control what gets released to UAT or Production and prevent developers trying to slip in last minute code changes that haven't gone through proper change/testing procedures. Only source code checked into the second repository will be compiled and released to our UAT/Production systems.
You can't 'slip' a change in anywhere in svn, since if you check out by
revision number you always get the same thing regardless of anything
anyone modified subsequently - and you can easily see the history, which
you'll lose in an export. Generally you would copy to a named tag in
the same repository just to have something easier than a big number to
identify it. You just need to use the tag and/or revision number to
identify what you tested. A typical scenario might be to copy to a
pre-release branch to freeze features for the testing process and then
you could have a qualified QA person copy the final tested version to a
tag under a path not writable by developers - you don't need a separate
repository for that, unless perhaps you are using file:// access to it.
--
Les Mikesell
lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-21 05:23:20 CEST