Rick Hillegas wrote:
The JCP requires that our JDBC4-exposing release can not be generally
available until the JDBC4 specification is finalized.
Is this something that the Derby community is bound to?
Here are proposed dates for 10.2 milestones:
August 10 - Feature work committed. 10.2 branch created.
August 24 - Last day to commit changes for 10.2
August 25 - Begin vetting 10.2 release candidate
September 15 - Target date for finishing the voting on Derby 10.2
What happens between September 15 and End of October on the 10.2 branch?
Does bug fixing and work on 10.2.1 begin?
If we fix critical bugs during that time in the 10.2 branch can't they
go into the release end of October?
End of October - Expected GA of JDBC4 with Mustang
End of October - GA of Derby 10.2. Release promoted to Apache mirrors.
