Hi Chris,
Thanks!
This process also applies when you open an issue that, when fixed, will
affect the UI or the behavior of the product in some way that needs to
be documented.
Regards,
-Paul
On 01/14/11 14:25, Chris Kasso wrote:
> Suppose you have an issue and it needs to be covered in the Release Notes
> or you just committed a change that modified behavior of the product and it
> impacts the docs - what do you do?
>
> A) Mention it to Paul when you pass him in the parking lot on the way
> home for the long weekend.
> B) Tape a yellow sticky note with the change detailed to your favorite
> writer's door.
> C) Who needs writers, the source is the only true documentation.
>
> Wrong, wrong and wrong.
>
> To facilitate ensuring last minute changes and additions are picked up by
> our talented set of writers please use the process outlined on the wiki to
> communicate changes:
>
> http://wikis.sun.com/display/GlassFish/iddocissues
>
> Thanks,
> Chris
>
--
Oracle <http://www.oracle.com>
Paul Davies| Principal Technical Writer| +1.408.276.3413
Oracle GlassFish Server Documentation
4140 Network Circle, Santa Clara CA 95054, USA
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment