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] [Commented] (DERBY-6061) Upgrade language is inconsistent
Date Tue, 05 Feb 2013 15:15:12 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571373#comment-13571373
] 

Kim Haase commented on DERBY-6061:
----------------------------------

Here's another thought: the Dev Guide topic "Soft upgrade limitations" is superfluous.

At releases 10.1 and 10.2 this topic described specific features of those releases that were
not available in a soft upgrade. Then for releases 10.3 through 10.5 this topic was not modified,
so the features list was obsolete. Then we took out the feature-specific text and pointed
readers to the release notes. Now almost all the information in that topic is also in the
previous topic ("Upgrading a database"), with the exception of a couple of sentences that
could be moved there.

I am going to revise the patch to make these changes -- what do you think?
                
> Upgrade language is inconsistent
> --------------------------------
>
>                 Key: DERBY-6061
>                 URL: https://issues.apache.org/jira/browse/DERBY-6061
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.9.1.0
>            Reporter: Kim Haase
>            Priority: Minor
>         Attachments: cdevcsecureroles.html, DERBY-6061-code.diff, DERBY-6061.diff
>
>
> In the Developer's Guide we describe two kinds of upgrade, "full" and "soft". I think
we used to use the terms "hard" and "soft", and "hard" was changed to "full" to provide a
more accurate description of what happens. There are still a few leftover occurrences of "hard"
in the docs here and there.
> However, "soft" doesn't provide much indication of what happens in that kind of upgrade.
Would "partial" be more correct? If not, is there a good alternative?
> I can go through the docs and fix the language based on whatever you all think makes
sense.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message