Andrew McIntyre wrote:
On 9/11/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
I can see two alternatives for us:
1. Ship 10.2 on the current schedule but do not include the JDBC4
drivers. When run on Java SE 6, Derby 10.2 would continue to expose our
JDBC3 implementation. In addition, we would remove JDBC4-specific
documentation from our user guides and prune out the JDBC4-specific
javadoc.
2. Delay the current 10.2 schedule until after JDK 6 goes GA. At that
time we could release a version of Derby which includes JDBC4 drivers.
Given the length of time since 10.1 was released, the uncertainty of the
exact date of JDK 6 shipment, and the number of new features included in
+1 to option one, then.
Should we plan to have another release with JDBC 4 once JDK 1.6 ships?
andrew
+1
I think that would be a great idea.
Regards,
-Rick
