Re: Baselines vs. labels

Eric Sedlar (esedlar@us.oracle.com)
Wed, 08 Dec 1999 09:55:49 -0800 

Message-ID: <384E9BA5.4D04CDBD@us.oracle.com>
Date: Wed, 08 Dec 1999 09:55:49 -0800
From: "Eric Sedlar" <esedlar@us.oracle.com>
To: Tim Ellison OTT <Tim_Ellison@oti.com>
CC: jamsden <jamsden@us.ibm.com>,
Subject: Re: Baselines vs. labels

1) To justify having a "baseline" concept in the spec, I think we need to have
    * a real customer scenario where the absolute guarantee a baseline will
never be changed is necessary, and
    * show that this is a significant enough case to warrant the complexity
2) Even if you can come up with 1), I would argue that the performance benefits
of a baseline should be available to whatever mechanism is used to represent a
release (currently a configuration) since I think that is going to be far more
commonly used, hence why something like the "baseline configuration" concept
I'm proposing might be a good idea.
3) I don't see anything in the spec preventing any WebDAV resource (baselines,
configurations, etc.) from being renamed by a user.  If you did, you would have
to reserve the entire namespace above the location of the baseline or whatever,
and make it appear as a read-only filesystem.

--Eric

Tim Ellison OTT wrote:

> <eric>
> >I don't see much utility for baselines if you can never
> >change the revision of a particular file in a baseline.
> </eric>
>
> It gives reproducibility/versioning at a macro level.
>
> <eric>
> <snip ... "performance benefits" ... "baseline configuration" ... >
> >If you want to prevent baseline configurations from being
> >changed, use access control.
> </eric>
>
> That doesn't give you version control, which is the objective.
>
> <eric>
> >Is the reason you consider labels less "reliable" than configurations due
> to
> >the assumption that you are protecting them with access control on a bunch
> of
> >different resources rather than access control on a single resource?
> >
> >Also, can an administrator rename baselines?
> </eric>
>
> My understanding was that administrators could not rename baselines (any
> more than they can rename revisions).
>
> <eric/><snip ... example >