Ron Petersen wrote:
>I am trying to find out if CVS can do the following:
>
>1. Does it support COBOL/370 and Assembler source code?
I has no special support for such files, it just treat it as any other
source code. CVS doesn't know of other file types than text and binary.
>2. Are there any limitations to the number of developers that can
> be making changes to a program concurrently?
No.
>3. Is there a mainframe interface to Panvalet?
Not as I am aware of
>4. Is there a mainframe build and compile component?
ditto
>5. Can CVS do PC syntax checks of all of the different types of
> supported source code?
No, not directly. But you can set up CVS to run other programs to do this
kind of tests during commit.
>6. Is there an automatic merging of source code when several
> developers (working in the same program) migrate their changes to
> various stages in the testing life cycle (i.e. unit, system
> and customer acceptance testing)? If merging of these program
> changes can only be done manually, is there any limitations to the
> number of versions which can be merged together?
>
CVS doesn't support configuration of a migration system. But you should be
able to use branches to solve this.
Merging between branches can be done automatically.
Conflicts must be corrected/confirmed manually (as always).
--------------------------------
Why not?
[EMAIL PROTECTED]
