On 4/25/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
ant elder wrote: > On 4/24/07, Simon Nash <[EMAIL PROTECTED]> wrote: > > <snip/> > > So I think it comes down to whether it is more important to put >> something out by JavaOne (in which case I'd be hesitant to call it >> "beta") or whether it is more important to attain a true "beta" level >> of quality even if that takes a little bit longer. > > > I guess a lot comes down to everyones slightly different perceptions > as to > what the name "beta" implies, what do others think about this? Should we: > > 1) continue aiming for a beta1 release around JavaOne timeframe > 2) continue with a beta1 release but take a bit more time > 3) aim for a release around JavaOne timeframe but change to a non-"beta" > release name, alpha-x or maybe a numeric like 0.90? > > I probably favor (2) as looking at things people have said they'd like to > get done it seems unlikely to me we'll be ready by JavaOne anyway. > > ...ant > I think it would be good to "Release early, release often" :) and have a release around JavaOne for people to try our SCA 1.0 APIs and assembly support as well as our new SPIs, and after that have more frequent releases than we did in in the past, like a release every two months maybe, with smaller increments each time. I'm for a variation of your option (3)... refine the contents of the release first, then decide to call it alpha/beta/gamma/whatever based on what we've been able to put in that release.
Ok, is there anything on the list in the wiki [1] that we think either (a) must be in the next release or (b) need not be in the next release? The main things I think are in the (a) "must have" category is "define a clear set of runtime and extension APIs", and unless we're happy with just a source distribution also "decide on distributions, create build scripts". If all we want to do is get a release out quickly then maybe everything else could be slipped to the release after next. One problem is i don't think we can define a clear and stable extension API without having a few extensions working using it so we probably also need to get a few implementation and binding types working using the extension API (eg java, script, axis2 and rmi?). I guess we don't actually have to release those extensions in the next release though. ...ant [1] http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Next+Release+Contents
