[
https://issues.apache.org/jira/browse/DERBY-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase resolved DERBY-4206.
------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
10.5.1.2
Derby Info: (was: [Patch Available])
No comments received, so I'm assuming consent.
Committed patch DERBY-4206.diff to documentation trunk at revision 775270.
Merged DERBY-4206.diff to 10.5 branch at revision 775289.
> 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: 10.5.1.1
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Fix For: 10.5.1.2, 10.6.0.0
>
> 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
> - 10.5.2.0 - (689064): instance a816c00e-011c-7658-a92a-fffff0cfee85
> on database directory C:\sampledb
> There is no release 10.5.2.0 (not yet) -- this is the result of using a
> versionnumber string at 10.4.2.0 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 10.5.1.1 release
> Various other topics, mostly in Getting Started, have the 10.4.2.0 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.
