[
https://issues.apache.org/jira/browse/DERBY-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508973
]
Myrna van Lunteren commented on DERBY-2840:
-------------------------------------------
Unless someone objects I intend to take the approach of changing the heading.
Something like:
"Changes
List if issues that were fixed in 10.3.1.1. Some of these issues were existing
in earlier versions, some were introduced during the development of new
functionality. This excludes issues marked 'test'.
How does that sound?
Regarding SubTasks - I struggled with that a bit. But for some master tasks
remain open, and thus nothing would show of the work and changes that has gone
in. In some cases, the release notes could be appended to subtasks, I think
(no, I don't have any specifics).
In the end, I decided that if it was a big enough task to warrant it's own task
jira, it warranted a separate mention.
> 10.3.1.0 RELEASE-NOTES "Bug Fix" section's contents do not match the title or
> description
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-2840
> URL: https://issues.apache.org/jira/browse/DERBY-2840
> Project: Derby
> Issue Type: Bug
> Components: Build tools, Documentation
> Affects Versions: 10.3.1.0
> Reporter: Daniel John Debrunner
> Assignee: Myrna van Lunteren
>
> A list of Jira issues in the release notes are introduced with:
> 'Bug Fixes
> The following issues are addressed by Derby release 10.3.1.0 beta. These
> issues are not addressed in the preceding 10.2.2.0 release."
> The list of issues contains items that:
> - are not bug fixes:(e.g. DERBY-2794, DERBY-2772)
> - are bug fixes that did not exist in 10.2.2.0 or early releases since
> they are related to fixes in new functionality (e.g. DERBY-2706)
> Note sure if the fix is to change the description to be a list of changes
> made for 10.3, or to only report bug fixes that have an affects field for
> 10.2.2.0 or earlier.
> Which ever approach is taken, I also wonder if sub-tasks should not be shown
> at all, since they tend to be a work management aid for developers, not
> intended for end-users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
