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.
*What's new in a new product*: We're releasing a very new version of our
product that resembles the old product, but is a new paradigm. I realize
that I can't remember ever writing release notes for a new release. Our
release notes typically have these sections: What's new (new features),
Resolved issues (bug fixes), and Known issues. There won't be any resolved
issues. There is a short list of known issues. But we're thinking about
what to say for "what's new" -- a list of features, a descriptive intro to
the product, a comparison to the old product... TPTB will make the final
decision about messaging, but I'm looking for ideas to propose.
*Cloud-based product release notes*: A separate but related question: Any
best practices for release notes for cloud -- updating on a rolling basis,
reduce friction, probably not as formal as our pre-cloud relnotes? (I'm
deliberately leaving out our current process for now.)
Thanks for any thoughts or pointers!
Sharon
sharon -dot- metzger -at- gmail -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com