On Aug 3, 2005, at 11:19 PM, Troy Simpson wrote:
>> From: Ben Collins-Sussman [mailto:sussman@collab.net]
>> Sent: Thursday, 4 August 2005 2:12 PM
>> Why not have the secretary mount the repository directly and
>> write to it? That's what subversion/webdav define as
>> "autoversioning".
>>
>
> We want the secretary to *only* mount the 'Working' folder in the
> repository
> so that #1 the files in 'Current' are not worked on directly, and
> #2 the
> filesystem isn't used to directly copy the 'Current' folder into a
> subfolder
> in the 'Archive' folder (where you subsequently lose all history on
> the
> copied version of the files). Our script ensures the transition from
> current-to-archive and working-to-current is done in an orderly
> fashion.
>
> We will be running the repository differently when we set it up for
> the
> development team - we will be using subversion clients (such as the
> repo
> browser, TSVN, eclipse plugin etc.) and working copies, but for the
> not-so-computer-savvy, this is out of the question - especially
> when this
> thing will be setup where temporary contract staff may be updating
> files in
> the repository.
>
> I know that subversion was never meant to work in this way, but it
> would be
> nice if the suggestion was taken seriously and a switch was added
> to the
> copy command to allow forced overwrite.
>
Perhaps you can create a special branch for the secretary, and let
her mount that branch. Then, using autoversioning, she can make any
changes she wants via drag-n-drop. When she's done working, someone
who knows Subversion can run 'svn merge' to port her branch changes
to the trunk (or 'current', or whatever you call it.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 4 14:56:45 2005