"Erik Huelsmann" <ehuels_at_gmail.com> wrote on 10/21/2008 02:44:26 AM:
> On Tue, Oct 21, 2008 at 3:17 AM, Toby Thain <toby_at_telegraphics.com.au>
wrote:
> >
> > On 20-Oct-08, at 5:18 PM, David Weintraub wrote:
> >
> >> I second (or is it third?) this motion.
> >>
> >> Tags are pain to work with. They are simply branches which people
> >> promise not to modify. There's also no easy way to prevent users from
> >> corrupting them (except through a custom pre-commit hook).
> >
> >
> > Actually path-based policy is an easy way.
>
> I agree with that. svnperms.py (a hook script) fully supports the
> use-case of "create but not modify" this node.
The concept of a "moving label" for integration, or minor updates
also must be done differently. Instead of just re-applying a label to
a different version, you either need to re-tag, delete and re-copy,
or merge. Depending on what is needed, this can be a multi-step
and more complicated process than other CM systems that have
first class labels.
Now granted, this is probably a "better" process, but one that
is foreign to a large number of people I have dealt with. (You
can lead a horse to water, but can't make him drink.)
Something like svnperms.py does work, but if I'm using LDAP
for authentication, the svnaccess file for authorization and
now svnperms.py for action based control, I now have to
maintain 3 separate username files. When you have 3000
users and hundreds of groups this isn't practical.
I'm reminded of a previous company I worked for that did
not allow engineers to do any user interface design. Engineers
will usually create something that only other engineers
are comfortable using. It may be fully functional and
incredibly powerful, but the casual user is going to just
sit and scratch their head in confusion...
Kevin R.
Received on 2008-10-21 16:35:40 CEST