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'll second this. Don't mention the unresolved issues in the release notes if
you can avoid them; concentrate on the resolved ones. If policy dictates that
they must be listed, describe them as known but unresolved. You will already be
annoying the person who originally reported the issue enough by saying it hasn't
been resolved without rubbing salt in the wound by saying you haven't even
bothered to look into it.
Gene Kim-Eng
----- Original Message -----
From: "Bill Swallow" <techcommdood -at- gmail -dot- com>
.> Ah, interpretation... I'm not going to answer your question. Instead
> I'll just offer advice:
>
> Don't include unresolved bugs in the release notes.
>
> does your company have an online bug base? Do customers have the
> ability to log in and see the status of their reported bugs? If not,
> look into it. If so, your work is done (with regard to unresolved
> bugs).
>
> IMHO, release notes should focus on what IS in the release and not on
> what isn't.
>
> I'd personally not like to look at the ingredients list on a box of
> Froot Loops to see "Non-Ingredients: real fruit, ground beef, lamb's
> tongue, lard, wood chips, roofing tar..."
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-