Both of these seem like useful suggestions. There's a scheduled IRC next Monday so lets discuss the release contents at that, in the meantime people could add their names to wiki items [1] for things that they want to get into the next release.
...ant [1] http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Next+Release+Contents On 4/25/07, haleh mahbod <[EMAIL PROTECTED]> wrote:
A working release that is closer to 1.0 spec version sooner would be better than having more content and a later release. M2 is old now and has issues. Should IRC be used for a discussion on release or maybe we should update the Wiki page with (IN/Out) comment to help you? If an item has both IN and OUT, discussion can resolve it. Would it help if we put our name next to the idea that each of us are driving? I sign up for wiki and driving the documentation layout and some of the content like user guide. On 4/25/07, ant elder <[EMAIL PROTECTED]> wrote: > > 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. > > > > Thoughts? > > > I've started a wiki page to track the next release contents: > > http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Next+Release+Contents > . > Very rough to start with - I've just tried to note all the things that > have > been suggested on the mailing list that we should put in the next release > (sorry if i've missed something, please just add it). > > JavaOne is just 8 working days away so to make a release by then, or even > just a release candidate, there is a lot to do if we want to finish > everything on that wiki page. What is the absolute minimum we should > include? What are must do's for you before I can tag or branch SVN for the > release? What on that list do you think we could leave out? > > ...ant >
