Hypothesizing that the reason the issues didn't make it into the release
notes was that they had been resolved but not closed, I've closed those
two issues. Maybe that will help.
Kim
On 10/26/12 11:01 AM, Kim Haase wrote:
Hi, Kathey,
Thanks, the release notes look great. I just checked the list for doc
issues. I'm not sure how doc issues get into the release notes, but a
couple of fixes that were backported to 10.8.2.3 didn't get into this
draft:
https://issues.apache.org/jira/browse/DERBY-5925 (Document derby.log
changes resulting from DERBY-5240)
https://issues.apache.org/jira/browse/DERBY-4229 (encryptionKeyLength
connection attribute should be documented)
Both of them were also backported to releases farther back than 10.8 --
but there was at least one more in that situation (DERBY-1721) that did
make it in. A puzzle.
Kim
On 10/24/12 07:13 PM, Katherine Marsden wrote:
Hello Derby-dev,
Attached are the draft release notes for 10.8.3. They actually say
10.8.2.3 because until I merge the versions the tool cannot be generated
with 10.8.3 as the release version.
Please review. I do have one question on the tool and generation. The
output says one issue was "disqualified". Is there a simple way to tell
which one and why are issues disqualified? Is it because the issue is
also marked fixed in an earlier version?
[generateReleaseNotes] // Filter id: 12322780, user id kmarsden
[generateReleaseNotes] // Filter issue count: 80
[generateReleaseNotes] // Issues written: 79
[generateReleaseNotes] // Issues disqualified: 1
[generateReleaseNotes] // Issues with release note: 2
[echo] Release notes written to C:\cygwin\svn\10.8/RELEASE-NOTES.html
Command for generating was:
$ant -Drelnotes.src.reports=C:\\cygwin\\svn\\10.8 -Djira.user=kmarsden
-Djira.password=xxxxx -Drelease.version=10.8.2.3
-Djira.filter.id=12322780 genrelnotes
