I'm a real newbie at this release cycle stuff, but my na�ve suggestion is to skip Turbine 2.3 and all the work it would take to tie Plexus into the Turbine 2.2 core (I have no clue how much work it would be, perhaps it would be really easy, I dunno), and instead go from Turbine 2.2 right into Turbine 3.0 which starts afresh with the Avalonized/pipeline-enabled design.
The Avalonized Turbine stuff seems, to me, radical enough to warrant a major release, not an update within the 2.x line. If the OJB support is really wanted in Turbine 2.x, a 2.2.5/2.3 release with OJB support would make sense, but I would still think any Plexus stuff should be pushed off to T3. - Stephen > -----Original Message----- > From: Eric Dobbs [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 25, 2002 6:54 PM > To: [EMAIL PROTECTED] > Subject: [PROPOSAL] Turbine Road Map > > Things are a bit confusing right now. We have an incomplete > decoupling of Turbine 2, and our development resources are > spread thin between two versions of Turbine, the old coupled > services, Torque, Maven, and of course our regular jobs. > > Those of us in the know are not alarmed about it. But the > general users are not in the loop. I'd like to decide on a > roadmap and loudly publish it so everyone knows what we're > up to. > > So here's a proposed roadmap. > > > Today we have Turbine 2.1. > coupled Torque > coupled Fulcrum > > Real soon now we'll have Turbine 2.2 > decoupled Torque > coupled Fulcrum > > Next step will be Turbine 2.3 > decoupled Torque > support for OJB included > coupled Fulcrum and services deprecated (for backward compatibility) > Plexus container for the components > Components migrated from decoupled Fulcrum > other Avalon components can also be used in Turbine and vice > versa > > Turbine 3 > Security has been decoupled into a separate component > coupled Fulcrum is gone > OJB support continues > Torque support continues > Plexus continues > Components continue > > > What do you think about these milestones? > > -Eric. > > ps. A brief primer on Avalon and Plexus. > Avalon has many different containers: Phoenix, Merlin, Fortress, > Tweety, MicroContainer. There may be more. The containers are > responsible for managing the lifecycle of the components they > contain. Plexus is another container. You can get the code > here: > http://tambora.zenplex.org/cgi-bin/cvsweb.cgi/plexus/ > > You can look at the Avalon framework to see what the lifecycle > interfaces are about: > http://jakarta.apache.org/avalon/api/index.html > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
