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:Re: PDF filenames - include release designation ? From:Robert Lauriston <robert -at- lauriston -dot- com> To:TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 29 Oct 2015 08:34:27 +0100
There are lots of regulated environments where the source code is
proprietary information not accessible outside of engineering. I guess
you're talking about environments where open source is part of the
I've yet to work anywhere where the source code repository wasn't
separate from the distribution package repository. They were linked by
build scripts but no one outside of engineering had a login for the
On Wed, Oct 28, 2015 at 9:08 PM, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> If you're working in a regulated environment (DoD, FAA, FDA, etc.), there's
> no such thing as "doesn't belong in source control." The release package for
> every document revision consists of the source files and the generated
> files. Because that's where everyone who distributes a generated file is
> supposed to get that file.
> In non-regulated environments, most content management systems provide
> similar controls.
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com