2 "how to <> in CVS" questions

[Mark O'Brien]

Hello all.

I am trying to figure out how to implement an automated process in which,
just prior to checkin approval, the branch is verified. Then after checkin,
the bug number is attached to that new file version.

Any ideas or suggestions are greatly appreciated.

1. Given a bug number on checkin, CVS will query the bug tracking tool to
get the branch the bug is to be fixed in, check to see if the bug is in the
correct state, then CVS will validate the branch in the current checkin
operation is correct. This all would be done in the checkin pre-op trigger.

Question: How to implement the branch validation part.

2. If checkin is successful, the bug number should be somehow attached to
that new file version (not by the developer and we want to ensure the
validated bug from checkin is used).

Question: How could this be implemented in CVS?

3. In general, does anyone have any resource that describes how to automate
the baseline generation (add new versions for specified bug #'s on top of
previous baseline) for and automated build system in CVS?

Thanks all,

Mark