Re: Re: Revised 10.2 plan for uncoupling the Mustang and Derby release trains
On 6/30/06, Jean T. Anderson <[EMAIL PROTECTED]> 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
Re: Revised 10.2 plan for uncoupling the Mustang and Derby release trains
This looks good to me, +1. Thanks to everyone for their hard work on resolving this. David 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. Regards, -Rick
Re: Revised 10.2 plan for uncoupling the Mustang and Derby release trains
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: Revised 10.2 plan for uncoupling the Mustang and Derby release trains
July towards the middle (after the Sun shutdown) Andrew McIntyre wrote: On 6/30/06, Rick Hillegas <[EMAIL PROTECTED]> wrote: 1) Lance will publish his proposed final draft (PFD) of the JDBC4 spec under the "early access" license. Is there a rough time frame for this, considering it's the gating factor for getting the release train rolling? Is it safe to assume that this will happen before August 11? Or is there a chance that the generation of the first release candidate may be later than August 11 if the PFD is not posted by then? +1 to the rest. andrew
Re: Revised 10.2 plan for uncoupling the Mustang and Derby release trains
Andrew McIntyre wrote: > On 6/30/06, Rick Hillegas <[EMAIL PROTECTED]> wrote: > >> >> 1) Lance will publish his proposed final draft (PFD) of the JDBC4 spec >> under the "early access" license. > > > Is there a rough time frame for this, considering it's the gating > factor for getting the release train rolling? Is it safe to assume > that this will happen before August 11? Or is there a chance that the > generation of the first release candidate may be later than August 11 > if the PFD is not posted by then? If the licence is not ready then we can have a release candiate that is marked alpha/beta, and thus would be an alpha/beta release if the vote passed. This probably would be the plan if the licencing change did not happen and Derby's GA was delayed until after Mustang. Dan.
Re: Revised 10.2 plan for uncoupling the Mustang and Derby release trains
On 6/30/06, Rick Hillegas <[EMAIL PROTECTED]> wrote: 1) Lance will publish his proposed final draft (PFD) of the JDBC4 spec under the "early access" license. Is there a rough time frame for this, considering it's the gating factor for getting the release train rolling? Is it safe to assume that this will happen before August 11? Or is there a chance that the generation of the first release candidate may be later than August 11 if the PFD is not posted by then? +1 to the rest. andrew
Revised 10.2 plan for uncoupling the Mustang and Derby release trains
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. Regards, -Rick
