[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: the obliterate discussion - why dumpfiltering is no valid workaround

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2007-07-21 18:57:45 CEST

Andy Levy wrote:
>> I took it the other way. Financial transactions need a real audit trail
>> so there's a good argument for saying that mistakes and their
>> corrections should be tracked forever.
> This is where I am as well. I work for a company traded on the NYSE,
> which means we're subject to lots of Sarbanes-Oxley review. My
> auditors would not be pleased if there was an easily-accessible way
> for people to permanently remove things from Subversion - they were
> absolutely giddy when they heard that that people (other than the
> repository admin, who needs to go to quite a bit of trouble) can't
> delete elements AND their history.
> if I lost this measure of control, their faith in my change-control
> procedures and monitoring would be shaken.

I don't think anyone has suggested that anyone but the repository admin
should be able to clean it up - although if it matters you should note
that anyone with file-level access can do things they probably
shouldn't. The question is, when the admin decides the cleanup is
necessary, should it require the space, effort, and downtime that a
dump/filter/load cycle takes. This probably only really matters for
large repositories with 24x7 usage but I'd expect that to be fairly common.

   Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 21 18:56:56 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.