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, 12 Feb 2013 21:51:13 GMT

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

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

Haven't heard any comments in a week, so --

Committed patch DERBY-6061-3.diff to documentation trunk at revision 1445404. 

If there are any problems with this, please let me know. I plan to commit the code patch tomorrow
and resolve the issue, but I can reopen it if necessary.
                
> 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
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: cdevcsecureroles.html, DERBY-6061-2.diff, DERBY-6061-2.zip, DERBY-6061-3.diff,
DERBY-6061-code2.diff, DERBY-6061-code2.stat, DERBY-6061-code.diff, DERBY-6061.diff, DERBY-6061.stat,
DERBY-6061.zip
>
>
> 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