Re: maintaing a list of changes in User Guides between versions.

["Gene Kim-Eng" <techwr -at- genek -dot- com>]

I'm not aware of any industry requirements for a detailed list of 
document changes from version to version.  Preserving the source
and deliverable files for each version has always been sufficient
for every industry I've written in, and if you've done that you can
generate lists of changes fairly easily on the fly with document
comparison tools.

OTOH, if your company is moving toward some sort of knowledge
base repository system, being able to search metadata for a document
release that shows that some specific change was made (for example, 
changing the "C" release of some reference specification the product 
was supposed to comply with to the "D" release) would enable a KB 
user to enter that parameter into a search function and immediately
get a return that identifies that spec change has having taken place in
Rev F of your document.

Gene Kim-Eng



"Caroline Tabach" <caroline -dot- tabach -at- gmail -dot- com> wrote in message news:mailman -dot- 3157 -dot- 1170681771 -dot- 22513 -dot- techwr-l -at- lists -dot- techwr-l -dot- com -dot-  -dot-  -dot-