TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:VSS and other version control/checkout systems From:"Scudder, Beth" <beth -dot- scudder -at- retek -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 27 Apr 2000 13:52:39 -0500
Hi all,
I was asked to evaluate Microsoft's Visual Source Safe as something for our
documentation group to use. We need something - we're about fifteen people
now and there have been issues that would have been avoided with the use of
a checkin/checkout system like VSS.
If it matters, we produce files in HTML, Word, and RoboHelp. We've tried
PVCS Version Manager, which we have for the software developers, but had
problems with it and have even found that it sometimes changes file
extensions, so we're not wild about it for anything other than code.
I have two questions for you:
1. I've generally only heard good things about VSS. Are there any skeletons
in its closet I should know about? Little bugs or glitches that Microsoft
isn't going to mention?
2. I like to know what my options are. Does VSS have any viable competition
for this function? Does a cheaper, better (or slower, worse) alternative
exist?
I'd really appreciate your feedback on this subject. Let me know if I need
to provide more information in order to get more meaningful information.