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 should elaborate...everyone, including documentation, files each
software bug (called a PR) in a tracking system. How it is classified
as it is entered starts the determination. Once a week we have a
meeting called a "bug scrub" where QA, development, product and
project management, and documentation meet to go over each
outstanding bug. About two weeks before deadline, we extract the
still-open bugs and distrubute the outstanding list. A few days of
discussion ensues, the end-result of the discussion is the list of
bugs and their text that goes in the documentation.
> A and C (along with others) in consultation with each other.
>
> --- "Hickling, Lisa (TOR)" <lhickling -at- Express-Scripts -dot- com> wrote:
>
> > Quick poll for everyone! Who decides which changes to document in
> > release notes?
> > a. You or other tech writer in your supervisory chain,
> based on discretion and product knowledge
> > b. A non-tech writing superior somewhere in your supervisory
> chain
> > c. Project manager or internal change sponsor
> > d. Other, please indicate ____________________
John Posada
Senior Technical Writer
"So long and thanks for all the fish."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l
