Jason van Zyl <[EMAIL PROTECTED]> writes: > On Mon, 2002-07-08 at 05:05, Daniel Rall wrote: > > Martin Poeschl <[EMAIL PROTECTED]> writes: >> >> > i'm not sure what the timeframe for a 3.0 release is .. there are some >> > users who don't want to use any packages marked as alpha or beta .. i >> > think we must shorten our release cycles!! >> >> I am willing to help out with a real beta release of 3.0, based on >> either Fulcrum or an Avalon container. > > I definitely think the Avalon container is the way to go. There are two > containers here: > > http://tambora.zenplex.org/cgi-bin/cvsweb.cgi/plexus/ > > One based on Fortress and one based on Tweety.
The one (which I assume is) based on Fortress looks copacetic. >> Is there a Turbine 3.0 TODO >> list enumerating the minimal requirements for such a release >> milestone? > > A standardized requirements document would be good. Yes. I'm willing to work on this if you'll toss in a few requirements. I'd like to hear from the rest of you on this as well. >> If not, is there any preference for where I should put it >> in the jakarta-turbine-3 CVS repository? > > I think that's as good a place as any. Okay. But where within the repo? At the root level, or as an xdoc? ... > Dan, I know you are used to working with HEAD so at least this way we > could organize something. > > As far as Turbine, there is the plexus container and a little bundle of > what I would like to see for Turbine 3.0: > > http://jakarta.apache.org/~jvanzyl/t3-jvz.tgz I'll try to find time to look, but I'd prefer an english description. :) > It is entirely stripped down (~30k) and I know that what is currently in > t3 is important for the apps you're involved with. What currently > exists for t3 is still really t2 cleaned and still doesn't satisfy the > requirement of full decoupling or ease of use. Will you describe how you can strip further T3 and maintain backwards compatibility? I haven't looked through the tarball yet and am sure there are answers in there, but am hoping to get some requirements out of your description. >> If so, how does this schedule compare with the T3 TODO list? > > I think the first requirement is to get the build and documentation > system together. Of course, as per usual this has taken longer than > expected but the Jelly'ized version of Maven is working now. And > with heavy weights like Bob McWhirter and James Strachan working on > Maven now it won't take long. Indeed. I'll kibitz with you on IRC about this. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
