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.
(I checked the archives and didn't find what I was looking for, so with
trepidation I post this message!)
Are there (legal or other) standards to consider when producing
documentation for beta versions of a software product? More
specifically, is it essential to put the word "beta" next to the version
number in the footer of the beta documentation on every page? Or is
simply putting the word "beta" on the cover enough?
Even if there are no set standards, I would appreciate hearing what
other companies do. Feel free to post to me directly, or the list (if
you think the topic would interest others).
Thanks!
Michal (Marta) Berman
Documentation Manager
New Dimension Software
michal -at- telaviv -dot- ndsoft -dot- com
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
