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.
In our organization, issues thought to be important for Release Notes
are submitted by the software engineers, software architects, and QA
engineers. These issues are reviewed in triage by the Product
Development Director, QA Manager, a senior Architect, and a Tech Pubs
representative, usually the TP Manager. The Tech Pubs manager, and/or
assigned writer(s) then works with the SMEs to properly document each
issue in the RN. We usually aim to have a first draft done by the time
of the first Release Candidate build.
~Victor
-----Original Message-----
From: techwr-l-bounces+vsolano=avolent -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+vsolano=avolent -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Ladonna Weeks
Sent: Monday, June 26, 2006 10:49 AM
To: 'Hickling, Lisa (TOR)'; 'Techwr-L'
Subject: RE: Quick Poll - Release Notes
D. The software manager decides and writes the notes. I (the technical
writer) look them over and sometimes suggest changes (which are usually
accepted). The decision is not built into our change management system.
-----Original Message-----
From: Hickling, Lisa (TOR) [mailto:lhickling -at- Express-Scripts -dot- com]
Sent: Friday, June 23, 2006 8:38 AM
To: Techwr-L
Subject: Quick Poll - Release Notes
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 ____________________
Tell us too, please, whether the document/do not document decision is
built into your change management system. For example, is there a
checkbox or similar field in your change request software that serves as
your indicator?
Thanks for your input!
Lisa H.
GTA, ON
******* Confidentiality Notice *******
ESI Canada -- Optimizing the value of drug and dental benefits
This email, its electronic document attachments, and the contents of its
website linkages may contain confidential health information. This
information is intended solely for use by the individual or entity to
whom it is addressed. If you have received this information in error,
please notify the sender immediately and arrange for the prompt
destruction of the material and any accompanying attachments.
******* Avis de confidentialite *******
ESI Canada -- Optimiser la valeur des regimes d'assurance medicaments et
dentaires
Ce courriel ainsi que tout document y etant joint de meme que le contenu
des liens vers des sites Web peuvent reunir des renseignements
confidentiels sur la sante. Cette information s'adresse uniquement a
l'usager ou a l'organisation auxquels elle est destinee. Si vous avez
recu ce message par erreur, veuillez en aviser l'expediteur
immediatement et proceder a la suppression du document et des fichiers
joints sans tarder.
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
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
