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-6061) Upgrade language is inconsistent
Date Mon, 04 Feb 2013 22:22:13 GMT

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

Kim Haase updated DERBY-6061:
-----------------------------

    Attachment: cdevcsecureroles.html
                DERBY-6061-code.diff
                DERBY-6061.diff

Here are two minimal patches that remove references to hard upgrade.

DERBY-6061.diff removes a sentence from the "Using SQL roles" topic (cdevcsecureroles.html):

M       src/devguide/cdevcsecureroles.dita

DERBY-6061-code.diff removes the word "hard" from one of the messages in the code:

M       java/engine/org/apache/derby/loc/messages.xml

This may be all that is needed.
                
> 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