On Sep 9, 2007, at 18:29, Bob Aiello wrote:
>> > ahh.. that makes sense - Thank you.
>> >
>> > I just found that a user deleted a branch and was making
>> > changes directly on the tag itself. Do you have suggestions
>> > for how to prevent this?
>>
>> Per-directory access control and deny write access on /tags to all
>> except the people permitted to create tags.
>
> I am just going through all the great responses.
> Thank you very much.
>
> I am going to look at the trigger next.
>
> I am not thrilled about denying write access to tags
> because I view tagging as a developer "signing"
> his/her work. So I really want the developer to
> do the tag. For now I am requiring both the URL and
> the Revision number.
>
> So this is where commercial tools like ClearCase and
> Accurev really do add value (especially for large organizations).
Not familiar with ClearCase and Accurev. I'm sure they do things
differently than Subversion in some areas, and I would certainly hope
that you get something for your money. However, relating to your
specific request that tags be immutable once created, Subversion can
handle that. Several such scripts have been posted to this list over
the years. See if this helps you:
http://www.google.com/search?q=site%3Asvn.haxx.se%20pre-commit%
20modify%20tags
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 10 03:08:52 2007