db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-379) Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby
Date Tue, 10 Oct 2006 10:15:21 GMT
     [ http://issues.apache.org/jira/browse/DERBY-379?page=all ]

Kristian Waagan closed DERBY-379.

    Assignee: Jeff Levitt

> Doc review (CLOSED TO FURTHER COMMENTS):  Getting Started with Derby
> --------------------------------------------------------------------
>                 Key: DERBY-379
>                 URL: http://issues.apache.org/jira/browse/DERBY-379
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>         Environment: all
>            Reporter: Jeff Levitt
>         Assigned To: Jeff Levitt
>            Priority: Minor
>             Fix For:
>         Attachments: derby379modified.diff
> This issue tracks comments for the Getting Started with Derby manual. The deadline for
posting comments was Tuesday, June 28, noon Pacific time.
please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate
additional comments.
> Some guidelines to follow when posting comments to this issue are:
> - Try to make clear and concise comments about what you want changed whenever possible.
 Provide concrete comments that say "Please change <original> to <modified>" instead
of generic comments like "This section needs to be rewritten."
> - If you're reviewing the HTML Files copy, include the URL for the page in the review
comment. Obtain the URL like this:
>     * highlight the topic in the left frame
>     * right click
>     * choose "Properties"
>     * copy and paste the address in the pop up box.
> - If you're reviewing the PDF copy, in the review comment:
>     * Include the page number for the PDF, and indicate whether the number is the PDF
sheet number or the printed page number.
>     * Include the title of the section that the problem occurs in. If it's in a subsection,
try to include the hierarchy of titles.
> - Please don't review the HTML Book copy -- it'll be time consuming to match up that
copy with the underlying DITA source.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message