Re: Revised 10.2 plan for uncoupling the Mustang and Derby release trains

["Jean T. Anderson" <jt...@bristowhill.com>]

Rick's plan looks good to me as long as the license is resolved -- and
it looks like it will be (with time to spare) given Lance's
clarification of the mid July target in
http://www.nabble.com/Re%3A-Revised-10.2-plan-for-uncoupling-the-Mustang-and-Derby-release-trains-p5125470.html

 -jean

Rick Hillegas wrote:
> Thanks to everyone for their suggestions and patience. After discussing
> the JCP issues with many people, including Geir Magnusson and Lance
> Andersen, I would like to propose the following approach for uncoupling
> the Mustang and Derby release trains.
> 
> 1) Lance will publish his proposed final draft (PFD) of the JDBC4 spec
> under the "early access" license.
> 
> 2) In mid-September the Derby community will vet and publish a GA 10.2
> release which implements PFD apis.
> 
> 3) The Apache web page describing 10.2 will start out saying that Derby
> drivers implement PFD apis.
> 
> 4) If no relevant changes are made to the PFD by the time Mustang goes
> GA, then at the end of October we will update the Apache web page so
> that it says Derby drivers implement final JDBC4 apis.
> 
> 5) If, however, the final draft changes in some way which affects Derby,
> then we will implement those changes in a follow-on bugfix release at a
> time convenient to the community.
> 
> Here again is the refined 10.2 release schedule which has attracted
> consensus:
> 
> August 10 : Last feature work committed. Branch created.
> August 11 : First release candidate generated.
> August 24 : Second release candidate generated.
> September 7: Third and hopefully last release candidate generated.
> September 15: Targetted end of voting on release candidates.
> 
> I hope we are converging on an acceptable plan. Thanks again for your
> patience.

Re: Re: Revised 10.2 plan for uncoupling the Mustang and Derby release trains

[Andrew McIntyre <mc...@gmail.com>]

On 6/30/06, Jean T. Anderson <jt...@bristowhill.com> wrote:
> Rick's plan looks good to me as long as the license is resolved -- and
> it looks like it will be (with time to spare) given Lance's
> clarification of the mid July target in
> http://www.nabble.com/Re%3A-Revised-10.2-plan-for-uncoupling-the-Mustang-and-Derby-release-trains-p5125470.html

Hadn't seen it mentioned on the list yet, but I checked and the
JSR-221 spec license now includes the language about marking
applications written to the specification with a notice. The language
is much clearer than the previous spec license. Thanks, Lance!

It's probably a good idea to add the notice required in the new spec
license to this page:

http://www.multinet.no/~solberg/public/Apache/DerbyJDK16/builds/

andrew