They look good from a docs perspective. I did notice that the paragraph
above the list of documentation bugs still says "10.10.1.4". That's the
only occurrence, though.
Thanks for the great work, Myrna.
Kim
On 3/26/2014 7:13 PM, Myrna van Lunteren wrote:
Thanks to everyone who reviewed!
And apologies for picking the wrong file to get the link.
Dag, the 'Issues' heading has been like this for many versions, and I
did not want to change it per se, but instead, I changed it to say
'Issues for Special Concern". I also moved it to the top, before the
Fixed Bugs.
I tried to address the other issues as well.
We've gone over keeping *all* changes in the release notes a couple of
times. The problem is we're using one file for all users, i.e. users who
are also running the derby tests (including ourselves) and end-users...
So in this case, I removed the test issues from the Release Notes, and
attached them as a separate file, RELEASE-NOTES_test.html, to DERBY-6218.
Let's try that link again (I stopped myself from checking in this time):
https://issues.apache.org/jira/secure/attachment/12637032/RELEASE-NOTES.html
Another look is appreciated!
I plan to generate candidate release artifacts tomorrow.
Myrna
On Tue, Mar 25, 2014 at 12:42 PM, Camilla Haase
<[email protected] <mailto:[email protected]>> wrote:
Hi, Myrna,
I found it in the branch too. Thanks for separating out the doc
issues -- that's very handy.
Your list of fixed doc issues coincides perfectly with mine except
for one ancient issue recently fixed:
https://issues.apache.org/__jira/browse/DERBY-4280
<https://issues.apache.org/jira/browse/DERBY-4280>
Thanks!
Kim
On 3/24/2014 8:57 PM, Myrna van Lunteren wrote:
Hi
I have created a draft for the 10.10.2 release notes and actually
checked it in for easy viewing, as well attached it to DERBY-6218:
https://issues.apache.org/__jira/secure/attachment/__12598328/RELEASE-NOTES.html
<https://issues.apache.org/jira/secure/attachment/12598328/RELEASE-NOTES.html>
It currently says 10.10.1.4, until I fiddle with the versions in
JIRA.
Because of a limitation in the number of issues that can
currently be
pulled from JIRA in an automatic fashion, I decided to split the
bugs up
into documentation, test, and code bugs, and I integrated them
manually.
We've not done this in the past and it's possible some issues are
incorrectly labelled.
Please review.
If you spot an issue that's been organized under the wrong
component,
please fix the component in JIRA.
Please let me know if you expect an issue to show up and it's
not, or
vice versa.
Thanks,
Myrna
