Tiago Espinha wrote:
Hi Rick,
I'm of the opinion we can close DERBY-4827. The most evident reference
to EBCDIC has already been fixed and we can come back to it if more
references are found in the future.
Thanks, Tiago. The issue is assigned to Kim so I would like to hear her
views as well.
Still regarding the 10.7.1 release, are we attempting to
include DERBY-4805 or will we leave that for a future release? I
reckon that for a proper change with testing, we are probably too late
to include it but I thought I'd throw the idea out there to get some
thoughts on it.
I wasn't planning to hold up the release for this issue, but if
something thinks that it's critical, please say so now.
Also, are we having a release note for DERBY-728? We aren't adding any
information to the manual regarding the UTF-8 support, so I think we
should at least have a reference somewhere saying that it is now
possible to use UTF-8 characters with the client driver.
If this bug is closed, then its one-line description will appear in the
release notes. I also updated releaseSummary.xml with a high-level
description of the 10.7 features. Here's what I said about this one
(feel free to improve this text):
<li><b>Unicode database names</b> - Remote clients can now use database
names which include unicode characters outside the ascii codeset.</li>
Is that good enough?
Thanks,
-Rick
Thanks,
Tiago
On Fri, Oct 22, 2010 at 5:15 PM, Rick Hillegas
<[email protected] <mailto:[email protected]>> wrote:
We're about a week and a half away from buddy-testing the 10.7.1
features: http://wiki.apache.org/db-derby/DerbyTenSevenOneRelease
Looks like we still have to wrap up the documentation which the
buddy-testers will need. The documentation issues for the
following features have been assigned but the issues have not been
closed:
o PlanExporter (doc issue DERBY-4758)
o UTF-8 support for client driver (doc issue DERBY-4827)
Can these issues be closed next week? If not, is there some way
that the rest of us can help out?
Thanks,
-Rick
