[ http://issues.apache.org/jira/browse/DERBY-1731?page=comments#action_12429704 ] Rick Hillegas commented on DERBY-1731: --------------------------------------
Hey Dan, can you clarify what you'd like to see here? The one-line description indicates some verbiage in the user docs (and the issue is marked as Documentation) but the issue is also flagged as needing a Release Note. Doing both sounds like a good idea to me. > Add warning to Derby docs that the JDBC 4.0 support is based upon the > proposed final draft of JSR 221 and might change in subsequent releases. > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1731 > URL: http://issues.apache.org/jira/browse/DERBY-1731 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.2.1.0, 10.2.2.0 > Reporter: Daniel John Debrunner > Fix For: 10.2.1.0, 10.2.2.0 > > > While JDBC 4.0 does not require any warning statement (see DEBRY-1639) it > would be good for Derby to have such a statement. > I think we want to freedom to match JDBC 4.0 final spec in a future 10.2 > release, a warning would help this, including stating that > applications written to JDBC 4.0 might need to be modified and re-compile to > work successfully. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
