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:Version control for parallel development From:SANDRA CHARKER <scharker -at- OZEMAIL -dot- COM -dot- AU> Date:Mon, 6 Mar 1995 03:56:09 +1100
A colleague is asking for suggestions about how to cope with this mind-boggling
situation:
* A customised billing system whose only "user" document was written
and has been maintained by the business analysts
* Existing documents written in Word for the Mac
* A two-month development cycle for new releases
* Overlapping development cycles for new releases
She is joining the team in a couple of weeks, at which time one release is
being coded and one is coming to the end of design. At this stage she doesn't
know if the different releases are limited to different parts of the system. If
they are, they might still affect the whole of the document set, depending on
how it's organised.
Does anyone have experience with writing and managing documents under cycles
like these?
Are there document management or version control tools for the Mac that might
help?
