[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Update by State
Re: Update by State
Wed, 12 Jun 2002 12:14:28 -0700
On Wed, Jun 12, 2002 at 01:43:28PM -0500, Karl Martin wrote:
> I am trying to use CVS in a corporate environment where the designation
> of a "released version" requires a set of permissions and controls.
> Some users are "read only", and they will have their WinCVS clients set
> up with sticky update options to always get the released version. Other
> users are "read write": they will be able to check in new updates of a
> file, but will not be able to change which version is the "released
> version". Only a few users will be "administrative releasers", able to
> set which version of a file is the released version.
> The State of a file, changed using 'cvs admin -s', is something that can
> only be changed by archive administrators, so it is attractive for this
> purpose. Tags are not attractive, as I don't think that file
> permissions can be set up so that any one user can check in files but
> cannot change tags.
Actually you can, using the taginfo administrative file in CVSROOT/taginfo.
I use it to restrict access to certain branches, as well as notify me
when any tag changes are made. It would be pretty easy to make it disallow
all tags except for certain users.
Send me an email if you'd like to see the script I use to restrict branch
access to certain users, it would be quite simple to modify it to allow
no tag changes. You can even put in an error message telling users what they
are doing wrong, it'll show up in their CVS client output.
> Can anyone give me any information regarding use of State in updates, or
> some other mechanism for marking files as released that is accessible as
> a sticky option for updates, but people who are able to check in files
> can still be restricted from changing the "released" mark.
Sorry I can't help with the use of State. I think taginfo can do what
you want though.