Selective updating with tags

[Richard Blair]

Two questions:

1) We're using non-branch tags to mark a golden release of our
database.  This release is not the tip, but is what users checkout and
and edit, until they are ready to commit changes and then the golden tag
will be moved on those files that were commited.  My question is this:
Once the golden tag has been moved, other users need to update their
work trees to incorporate the new golden changes, but NOT for the files
they are currently editing. Is there a way to force cvs update to be
selective and not update files that are being edited?  The biggest
problem I see is that if you update -r golden, you will undo revision
patches beyond that of golden.  For instance, if I am editing revision
1.5 and golden is tagged as 1.3, the update will un-patch 1.5 and 1.4
changes from the file I'm editing.

2) Second question, is there a better way to implement what we are
trying to do?  Basically we want our users to work with progressing
versions of a 'golden' database.  They are working independently, but
often on the same subset of files.  It's important that we maintain a
golden database, since we need to be simulating with a working one at
all times.

Thanks

Rich