Re: Validations in CVS

[Todd Denniston]

Khurram Rashid writes:
> This is a multi-part message in MIME format.
Please do not send MIME and/or HTML encrypted messages to the list, or even
to me directly.
Plain text only, PLEASE!

> I just wanted to know if there is any way in CVS to do 
>validation check in, i.e.
> Developer checks out a module from CVS
> Developer makes some changes in the code.
> Developer then checks in the module as validation check in.

> At this stage by validation check in I mean that the 
> module has to be reviewed by a validator before 
> finally committing the module in the repository. i.e.

No.
it is either committed (checked in to the repository) or it is not.

> Validator now checks out the module from CVS
> Validator validates the module
> Validator commits the module in CVS

You can however have a process using branches to implement this scheme using
cvs. Have a branch(or set of them) which the developers can commit to, have
another set of branches for the Validators to merge commits to and use
cvs_acls to prevent developers from committing to the validated branch.

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter