Thanks Paul.
Yes, let's do as you proposed. SQE will start testing the CLI manpage
and file bugs.
Paul, could you please let us know the following two things first.
(1) Which AS build has all the check in from doc team, so SQE should use
it for testing ?
(2) SQE will use the following link to start testing with new and
changed CLI commands first.
Could you make sure the link is up to date.
http://swpubs.sfbay/writing/appserver/as9/reviewdrafts/mpages/index.html
Thanks,
Judy
Paul Davies wrote:
>Hi,
>
>After looking through my notes and emails from previous meetings, I now understand better the source of Judy's concerns.
>
>The review shcedule for bundled documentation that was origianlly proposed was based on a misunderstanding on my part for which I apologize. When we discussed this schedule, I was unaware that after the MS4 code freeze, any changes before beta to the bundled docs would require a bug of priority no lower than P2.
>
>For the bundled docs that are already checked in to the build, I propose (as I suggested in the meeting) that SQE review and test the versions that are checked in to the build and use change requests to report errors and request changes. Unless the change request is a P1 or P2 bug, the doc group will aim to make the changes for RR.
>
>For bundled docs that were not checked in to the build, and for the unbundled docs, I will devise review schedules to ensure that they are adequately reviewed by RR.
>
>I can report that the JBI man pages were reviewed twice by engineering and SQE in the JBI team. The JBI online help has been reviewed by engineering in the JBI team.
>
>For the other new and changed man pages, I will look at the doc plans and contact the responsible writers for status and schedule information.
>
>Regards,
>-Paul Davies
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
>
>