Abstract
Software developers have used version control systems for years, to manage source code changes and to enable them to reproduce any given level of their software from the source code that created it. Most writing departments, however, tend to perform full-scale weekly backups at best or tempt fate by not performing any backups at worst. The two major reasons for this neglect of document version control are lack of adequate tools and the effort required by writers to deal with the inadequate tools presently available. This paper describes a tool I developed at IBM, the Automated Backup Manager (ABM), which attempts to connect the writer's documentation to a true source version control system, without reducing writer productivity.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
