Kathy Saunders wrote: > Rick Hillegas wrote: > >> Thanks, Kathy. I think I'm getting the message that the following >> would be an acceptable and more traditional schedule: >> >> August 10 : Last feature work commits >> 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 >> >> Is this a realistic schedule or is it still too aggressive? >> >> Thanks, >> -Rick > > In my opinion that is a reasonable schedule. Of course, number of > release candidates and final dates are dependent on the quality of the > code. But, based on what I've seen with Derby releases so far, this > timeframe seems like it can work. > > Hopefully the licensing issues will be resolved prior to August 10 as well.
A license that allows creating the release candidate must be in place before the release candidate is made available. Lance, how do these dates work from a licensing perspective? -jean
