db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manjula Kutty (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-380) Doc Review: Derby Developer's Guide
Date Mon, 27 Jun 2005 22:11:57 GMT
    [ http://issues.apache.org/jira/browse/DERBY-380?page=comments#action_12314554 ] 

Manjula Kutty commented on DERBY-380:

Please remove the following line from the developer's guide at http://incubator.apache.org/derby/docs/devguide/rdevdvlp38881.html

The sentence is this : Derby is always the subprotocol for connecting to a Derby Database

> Doc Review: Derby Developer's Guide
> -----------------------------------
>          Key: DERBY-380
>          URL: http://issues.apache.org/jira/browse/DERBY-380
>      Project: Derby
>         Type: Improvement
>   Components: Documentation
>  Environment: all
>     Reporter: Jeff Levitt
>     Priority: Minor
>      Fix For:

> This issue tracks comments for the Derby Developer's Guide. The deadline for posting
comments isTuesday, June 28, noon Pacific time.
> 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:
For more information on JIRA, see:

View raw message