Subject: documentation best practices
Message-ID:
1323082560.94393.yahoomail...@web114713.mail.gq1.yahoo.com
Content-Type: text/plain; charset=iso-8859-1
I could use some insight into a situation I haven't encountered before today:
how does one best respond to a request (read: order
A big hearty thank you (xie xie) to all who responded to my question about
including not-yet-released features in software documentation. The jury is
still out on how I'll handle the situation but your answers were helpful and
thought-provoking! This list is the
meusers.com"
Subject: documentation best practices
Message-ID:
<1323082560.94393.YahooMailNeo at web114713.mail.gq1.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
I could use some insight into a situation I haven't encountered before today:
how does one best res
A big hearty "thank you" (xie xie) to all who responded to my question about
including "not-yet-released" features in software documentation. The jury is
still out on how I'll handle the situation but your answers were helpful and
thought-provoking! This list is the BEST!
-- next
: Jeff Coatsworth jeff.coatswo...@jonassoftware.com
To: framers@lists.frameusers.com framers@lists.frameusers.com
Sent: Tuesday, 6 December 2011 3:51 AM
Subject: RE: documentation best practices
It's called marketing ;)
From: framers-boun...@lists.frameusers.com
) syed.hos...@aeris.net
To: Writer generic...@yahoo.ca; Jeff Coatsworth
jeff.coatswo...@jonassoftware.com; framers@lists.frameusers.com
framers@lists.frameusers.com
Sent: Tuesday, 6 December 2011 5:45 AM
Subject: RE: documentation best practices
Not necessarily, but usually, I suspect. J
In our
Don't know if anyone has mentioned this, but the reason why you're not
supposed to mention what will be in future versions is for legal
reasons. You should not make forward-looking statements because the
company could be held legally responsible for them. And since none of us
can guarantee what
@lists.frameusers.com framers@lists.frameusers.com
*Sent:* Monday, December 5, 2011 5:21:46 PM
*Subject:* RE: documentation best practices
It's called marketing ;)
*From:* framers-boun
Nicely put.
Nadine
From: Galanter, Lea lea.galan...@fticonsulting.com
To: framers@lists.frameusers.com
Sent: Tuesday, December 6, 2011 1:30:28 PM
Subject: RE: Documentation Best Practices
Don't know if anyone has mentioned this, but the reason why you're
At 02:56 -0800 5/12/11, hessiansx4 wrote:
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
From: Jeff Coatsworth
To: "framers at lists.frameusers.com"
Sent: Tuesday, 6 December 2011 3:51 AM
Subject: RE: documentation best practices
It's called "marketing" ;>)
From: framers-bounces at lists.frameusers.com
[mailto:framer
in (Syed.Hosain at aeris.net)"
To: Writer ; Jeff Coatsworth ; "framers at lists.frameusers.com"
Sent: Tuesday, 6 December 2011 5:45 AM
Subject: RE: documentation best practices
Not necessarily, but usually, I suspect. J
?
In our case, in some of our API specs, we sometimes send out
Don't know if anyone has mentioned this, but the reason why you're not
supposed to mention what will be in future versions is for legal
reasons. You should not make forward-looking statements because the
company could be held legally responsible for them. And since none of us
can guarantee what
Nicely put.
Nadine
>
> From: "Galanter, Lea"
>To: framers at lists.frameusers.com
>Sent: Tuesday, December 6, 2011 1:30:28 PM
>Subject: RE: Documentation Best Practices
>
>Don't know if anyone has mentioned this, but the
At 02:56 -0800 5/12/11, hessiansx4 wrote:
>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
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)
. Thank you for your cooperation.
From: framers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of hessiansx4
Sent: Monday, December 05, 2011 2:56 AM
To: framers@lists.frameusers.com
Subject: documentation best practices
I could use some insight
From: framers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of hessiansx4
Sent: Monday, December 05, 2011 2:56 AM
To: framers@lists.frameusers.com
Subject: documentation best practices
I could use some insight into a situation I
It's called marketing ;)
From: framers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of hessiansx4
Sent: Monday, December 05, 2011 5:56 AM
To: framers@lists.frameusers.com
Subject: documentation best practices
I could use
Subject: RE: documentation best practices
It's called marketing ;)
From: framers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of hessiansx4
Sent: Monday, December 05, 2011 5:56 AM
To: framers@lists.frameusers.com
Subject
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
mediately,
and delete or destroy all copies. Thank you for your cooperation.
From: framers-boun...@lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of hessiansx4
Sent: Monday, December 05, 2011 2:56 AM
To: framers at lists.frameusers.com
Subject: documentatio
1 425 743 8113
From: framers-boun...@lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of hessiansx4
Sent: Monday, December 05, 2011 2:56 AM
To: framers at lists.frameusers.com
Subject: documentation best practices
I could us
It's called "marketing" ;>)
From: framers-bounces at lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of hessiansx4
Sent: Monday, December 05, 2011 5:56 AM
To: framers at lists.frameusers.com
Subject: documentation best
That's what I was thinking. It sounds more like marketing copy than user guide
content.
Nadine
>
> From: Jeff Coatsworth
>To: "framers at lists.frameusers.com"
>Sent: Monday, December 5, 2011 5:21:46 PM
>Subject: RE: documentation
siansx4
Sent: Monday, December 05, 2011 2:56 AM
To: framers at lists.frameusers.com
Subject: documentation best practices
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
users.com] On Behalf Of Writer
Sent: Monday, December 05, 2011 2:27 PM
To: Jeff Coatsworth; framers at lists.frameusers.com
Subject: Re: documentation best practices
That's what I was thinking. It sounds more like marketing copy than user guide
content.
Nadine
amers at lists.frameusers.com"
> *Sent:* Monday, December 5, 2011 5:21:46 PM
> *Subject:* RE: documentation best practices
>
> It's called "marketing" ;>)
>
>
> *From:* f
28 matches
Mail list logo
