Re: PDF filenames - include release designation ?

[Robert Lauriston <robert -at- lauriston -dot- com>]

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
regulation?

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
source system.

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

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives