db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4206) Documentation: Release versions in output need updating
Date Fri, 08 May 2009 21:58:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kim Haase updated DERBY-4206:

    Attachment: DERBY-4206.zip

Attaching DERBY-4206.diff, DERBY-4206.stat, and DERBY-4206.zip, with changes to 7 files that
contain version-specific command output:

M      src/tools/rtoolssysinfo1002629.dita
M      src/devguide/cdevdvlp27715.dita
M      src/devguide/tdevdvlp20349.dita
M      src/getstart/twwdactivity1.dita
M      src/getstart/twwdactivity3_Setup.dita
M      src/getstart/twwdactivity2.dita
M      src/getstart/twwdactivity4.dita

Please let me know if any changes are needed. I'll commit in a week or so if no comments arrive.

> Documentation: Release versions in output need updating
> -------------------------------------------------------
>                 Key: DERBY-4206
>                 URL: https://issues.apache.org/jira/browse/DERBY-4206
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-4206.diff, DERBY-4206.stat, DERBY-4206.zip
> The topic http://db.apache.org/derby/docs/dev/devguide/cdevdvlp27715.html, "Booting databases,"
currently shows the following output:
> 2008-09-18 16:43:54.992 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby 
> - - (689064): instance a816c00e-011c-7658-a92a-fffff0cfee85
> on database directory C:\sampledb
> There is no release (not yet) -- this is the result of using a versionnumber
string at and having it automatically (and incorrectly) update to 10.5. It's better
to just hardcode the actual release number and then update the files post-release. The revision
number is release-specific, too.
> I'll update it now that we have an actual release
> Various other topics, mostly in Getting Started, have the version and revision
number hardcoded. It's time to update these, in the trunk at least.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message