It appears from Rick's mail that the release notes will get picked up only if the Jira issue is closed. I have release notes attached to DERBY-2967 but the issue is still open because it will be nice for us to add a test case for one specific scenario as mentioned in DERBY-2967. All the engine code and other test cases for DERBY-2967 have already been checked into the 10.3 codeline. So, I will go ahead and enter a new Jira entry for the test case and close DERBY-2967 so we can pick up the release notes.
thanks, Mamta On 11/26/07, Rick Hillegas <[EMAIL PROTECTED]> wrote: > Kathey Marsden wrote: > > I just checked in the release notes and changes files for the > > 10.3.2.0. One thing I noticed is that none of the issues have release > > notes. Please let me know right away if any issues are missing, > > release notes are needed or you see any other problems with the > > release notes. > > > > Thanks > > > > Kathey > > > > Sending CHANGES.html > > Sending RELEASE-NOTES.html > > Sending releaseSummary.xml > > Transmitting file data ... > > Committed revision 598379. > > > > > > > Hi Kathey, > > Here are a couple items: > > 1) DERBY-3086 doesn't appear in the list of fixed issues. I have changed > this issue from Resolved to Closed and marked the FixVersion field to be > 10.3.2.0. Hopefully that will make it appear in the query which creates > your JIRA input. > > 2) Ditto for DERBY-3176. > > 3) I don't know what to do about DERBY-3083. The regression introduced > by this issue is fixed although the JIRA itself is a long way from > resolution. > > 4) The syntax of the Issues paragraph is a little broken. > > Thanks, > -Rick >
