- run "cvs update -A" on these files to revert the working copy to the head=
.

This wouldnt work for me because i dont want to release the changes that ar=
e
on the "head". The revision that i want to release is an updated version
from the previous release. The one on the 'HEAD' could be one that someone
has updated and is not to be release for the next 3 release.

- The tag needs to be made into a branch
I wish i can do this but i cant seem to be able to convince any of my bosse=
s
that we should support branching. We dont support it because it apparently
makes things a lot more complicated than they need to be.

- Prevent people from checking in files that are not ready to be delivered
in the next release.
This might work as i would then be able to just checkout from 'HEAD'
everytime there is a new release.


Now my questions are as follows,

- Is there some way i can checkout using the above procedure without coming
across the "sticky tag is not a branch" error?
- Is there a better way i can achieve the same steps above without having t=
o
use branching?
- This sounds to like its one of the most common situations in a developmen=
t
environment. How do other people do it without using branching?
- And finally if you have any knowledge of subversion, do you know if it
works the same way and i will have the same problems if i change to
subversion?

Any help will be greatly appreciated.