Config Management/Version Control
User Rick Wellinghoff (RWELLINGHOFF@remember.com.nospam) posted:
We're trying to revise our CM process and I was hoping to get some input
from this group. We use MS Visual Source Safe for source control. What
structure of file groups would be recommended? How many different levels of
promotion are recommended (Dev, Release, Test, Production, etc)?
What info should SQA require (keeping in mind traceability and audits) when
code is presented for testing? i.e.: list of files that changed from last
release, appropriate owner/date/version info in each file, etc.
Thanks in advance