HP3000-L Archives

October 1997, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Eric Kundl <[log in to unmask]>
Reply To:
Eric Kundl <[log in to unmask]>
Date:
Sat, 18 Oct 1997 20:16:40 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
everyone,
we are considering getting some sort of Version Control / Documentation
package.
95% of our source code is Cobol and resides on a single HP3000 mpe/ix that
is used as the development cpu. We support about a dozen 'sites' that run
our software. We create numerous 'versions' of each program with small
changes (typically 30 small modifications per year) and 4 major 'releases'
of the whole system that is installed one at a time at each site as they
have time. So we normally have 3 or 4 'accounts' on our development cpu for
the various releases that the sites might be on.

Our auditors want more control than currently is in place.
We are looking at the Diamond Optimum systems VCS and Doc/3000 product and
the ROBOT systems version tracking product.

Does anyone have any thoughts on these 2? pros and cons? or maybe another
vendor with a product you think is good?

A quick review of the Diamond Optimum systems web site seems to indicate
the source code is stored in a database on an NT server and controlled from
there. My supervisor is not real happy about moving the source code off of
the HP3000 onto a server. Is this how it works? Is this good? or bad?

Any thoughts and ideas would be apreciated..
thanks-
eric kundl
[log in to unmask]

ATOM RSS1 RSS2