Best Practices in Indicating Versions

[jsokohl -at- mac -dot- com]

Hi,
So, anyone have research on best practices on indicating changed
documents? In the old old days, documentation departments used to issue
docs with multidigit version numbers, change bars, and change pages.
Later, tech writers did away with change bars and relied on summary paras
of "what's new" similar to Readme files. Then some folks did away with
these altogether relying instead on just the date of the document. Then
even these seem to disappear.

What are you doing that seems to work with your users? Any advice'd be
most appreciated.

Thanks,
joe

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

NEED TO PUBLISH FRAMEMAKER CONTENT ONLINE? "Mustang" is a NEW single
sourcing tool for FrameMaker that lets you easily publish your content
online. No macro language required! http://www.ehelp.com/techwr-l3

Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See www.mercer.edu/mstco or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot- 

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.