"freezing" a tag or branch tree

The two suggested methods below require server administrative access,
much more than committer access to the repository. The person making
the tag probably has no such access to the server. Indeed in a case
I'm working on the committer and server administrator don't even speak
the same *language* and are twelve hours apart.

(in an enterprise scenario the server is probably in the clutches of
the MIS department and can't be changed without a lot of paperwork)

I'm thinking of hacking the client to look for a property named
svn:nocommit and if it is present & non-nil then fail the commit and
return the property contents as an error message. If a committer
really needs to change a tagged tree they can remove or null the
property, making their changes, and set svn:nocommit again.

The specific scenario we're thinking of is someone in Sustaining
Engineering checking out a tag to reproduce a failure in the field,
fixing the bug and committing the fix without remembering to switch
to the right branch first.

A commit to tags/ will trigger an email notice to everyone so such a
mistake probably gets caught. But it's not hard to imagine other uses
for a "please don't" flag that can be set, and overridden as needed, by
committers.

From: Ben Collins-Sussman <sussman@collab.net>
Date: 11 Sep 2003 14:28:03 -0500
Subject: Re: svn:externals set to tag

"Jordan, Tom" <Tom.Jordan@camtronics.com> writes:

> Is there a way to "freeze" a tag and disallow further
> check-ins on that branch?

It's called access control.... :-) Just restrict commits to any directory
within /tags, for example.

Use a pre-commit hook script. Or use mod_authz_svn.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 17 22:52:51 2003