<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>As someone who both develops and documents software, I can only answer with a hearty “Hear hear!”. I think you’re exactly right, and I hope you can get them to see the light.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Good luck,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Lea<o:p></o:p></span></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><br>_________________________________</span><span style='color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Lea Rush</span><span style='font-family:"Calibri","sans-serif";color:#1F497D'> <br></span><i><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Software and Documentation Specialist</span></i><span style='font-family:"Calibri","sans-serif";color:#1F497D'> <br></span><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Astoria-Pacific International</span><span style='font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-family:"Calibri","sans-serif";color:black'><a href="http://www.astoria-pacific.com"><span style='color:blue'>www.astoria-pacific.com</span></a></span><span style='font-family:"Calibri","sans-serif";color:purple'><a href="http://www.a"><span style='color:blue'><br></span></a></span><span style='font-family:"Calibri","sans-serif";color:#1F497D'>ph: 800-536-3111</span><span style='font-family:"Calibri","sans-serif";color:#1F497D'> <br></span><span style='font-family:"Calibri","sans-serif";color:#1F497D'>fax: 503-655-7367</span><span style='font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-family:"Calibri","sans-serif";color:#1F497D'><a href="mailto:lea@astoria-pacific.com"><span style='color:blue'>lea@astoria-pacific.com</span></a><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#99CC00'>Please consider the environment before printing this email.</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#339966'>`·.¸¸.·´¯`·.¸.·´¯`·...¸ ><((((º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><((((º></span></b><span style='font-size:7.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:4.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <br></span><span style='font-size:7.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>NOTICE OF CONFIDENTIALITY<br></span><span style='font-size:4.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <br></span><span style='font-size:7.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>This communication is from Astoria-Pacific International and is intended to be confidential and solely for the use of the persons or entities addressed above. If you are not an intended recipient, be aware that the information contained herein may be protected from unauthorized use by privilege or law, and any copying, distribution, disclosure, or other use of this information is prohibited. If you have received this communication in error, please contact the sender by return email or telephone (503) 657-3010 immediately, and delete or destroy all copies. Thank you for your cooperation. </span><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com] <b>On Behalf Of </b>hessiansx4<br><b>Sent:</b> Monday, December 05, 2011 2:56 AM<br><b>To:</b> framers@lists.frameusers.com<br><b>Subject:</b> documentation best practices<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>I could use some insight into a situation I haven't encountered before today: how does one best respond to a request (read: order) to include something in their product's documentation about a functionality that will not be released with the upcoming release (it will still be in development) but is hoped to be ready "shortly" (whatever that means) after the product is released.<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>I've politely pointed out that industry best practice is to document what IS as opposed to what WILL BE and that certain liabilities might be incurred if promises are made and then something goes wrong. <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>Any thoughts?<o:p></o:p></span></p></div></div></div></div></body></html>