OK, back to the 10.2 release schedule. How about this:
early August - Feature work committed. 10.2 branch created. August/September - Proposed Final Draft of JDBC 4.0 goes public with updated evaluation license. Voting on a release candidate for 10.2 can begin as early as the day the PFD goes public September/October - GA of Derby 10.2.1, which includes whatever wording the spec requires regarding the JDBC 4.0 implementation in Derby. Release promoted to Apache mirrors. End of October - Expected GA of JDBC4 with Mustang, which includes a JavaDB version of Derby that is midstream between 10.2.1 and 10.2.2 November/December - Derby 10.2.2 follow-on release to remove the wording surrounding JDBC 4 bits that had previously been required by the spec license. Sound good? andrew
