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. > Is there a Turbine 3.0 TODO > list enumerating the minimal requirements for such a release > milestone? A standardized requirements document would be good. > 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. > An important part of any release is well organized documentation. > Previous releases of Turbine contained quite a bit of documentation, > but these hidden jewels were sequestered in the far recesses of the > jungle which was the Turbine 2.x web site, accessible only to those > with native guide and elephant, or to those brave souls stout enough > of heart to wade through the piranha infested waters of the source. > > Maven's XML descriptor and sharp DVSL machete promises to bring order > to our chaotic jungle, tempting us with a slick hierarchical layout. > But alas, its shaky rope bridge of stability has washed away every > time I've returned to ford the river of a build. The tease of web > site coherency is frustrating, to say the least. A stable build > system is without a doubt a Turbine release prerequisite. Seeing as > how Maven originally emerged from the Turbine jungle to statisfy > Turbine requirements, what are the chances that beta 5 approximates > release candidate quality, satisfying this most basic of requirements? In about a week. We've made the switch completely over to using Jelly. I've made two passes at the plugins, cleaning them up and this week there are about 4 of us working on it. Right now it is primarily a matter of documentation and sorting out the plugin structure as I would like b5 to be close to what is released for 1.0. > If this is an unrealistic expectation, is there any expected time > frame for a Jelly-based release candidate of Maven? Not unrealistic. I've basically been working on Maven and Turbine in tandem because I don't even want to attempt anything with Turbine until Maven is working. b5 is working now, I would like to move the descriptors forward because I always use Turbine as a guinea pig. I know that for most projects it's not a good idea to use CVS HEAD but again I would like to use Turbine as a test. 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 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. > 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. > > - Dan > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
