Hi Skip, The links give some reasoning behind why the the move away from the current code base for Turbine is a good idea. The complexity of the code is such that it is a lot of effort to maintain and improve on it. Lets not perpetuate that for too long. I did say plan, not migrate immediately. I know that I have to release a new version of my product based on Turbine in a few months. I'd rather move to something that has an architecture that is easier for commiters to maintain and also improve on, the Avalon base seems to give them that. Worth reading the Avalon guide to see what the underlying component framework is all about. Hey, maybe even I can contribute now that the code will be more understandable in a framework with proper lifecycle management. Look out for my Turbine coffee machine controller service ;)
So by all means release 2.2, personally I have avoided it due to the need to fiddle with CVS all the time, I patched the 2.1 code myself to fix the problems that affected me. So I am not stuck waiting for a release of 2.2, 2.3, 3.0 or anything. Maybe I am lucky that I hung out for this long and it gives me a choice on where I go from here. Since I like the arguments put forward by JvZ then I can wait for Summit. Regards David -----Original Message----- From: Skip Walker [mailto:skip@;gossamer-group.com] Sent: 19 October 2002 22:48 To: 'Turbine Users List' Subject: RE: What are Plexus/Summit? Oy! Deja vu. How many times are we going to do this? First off, let me say I haven't gone out to these Plexus/Summit links and read anything about Plexus or Summit. My reason, right now I don't care about the latest and greatest. I want what I've invested my time and effort in, Turbine 2.1 and Turbine 2.2 beta, and now fulcrum with Hennings DBSecurityService, to become a stable release. Turbine needs real releases to become a viable project again. It does not need another pie in the sky project that may never be released (See Turbine 3). Here's my ideal scenario for the way the Turbine revs should be rolled out: 1) in 2 months or less, Turbine 2.2 should be released. I'm not sure what are the major differences between 2.1 and 2.2, but ideally the only major change, other than perhaps package renaming, is the decoupled torque. Releasing 2.2 will give all the Turbine 2.1 users to get the latest bug fixes in a release, rather than from cvs (which is a process not all of us like). Additionally, it will give Turbine 2.1 users the opportunity to move to the decoupled torque if they have not already. Torque 3.0 would also be officially released at this time as well. 2) in 6 months or less, Turbine 2.3 should be released. This should include the Fulcrum services framework, especially Hennings DB Security Service proposal. Also, there are enhancements to the intake service, and a Security Policy service I've heard that might go in, but not at the cost of the 6 month time frame. (As an aside, I've successfully integrated Hennings DBSecurityService with my own custom legacy user table, and this process was relatively painless.) Releasing this version will provide those that have already invested in Fulcrum, a release that integrates with the framework, and also give people the incentive to move to Fulcrum. Only after Turbine 2.3 is released would I think it prudent to move forward. What Turbine needs is real releases, not new alpha and beta projects. Skip > -----Original Message----- > From: David Wynter [mailto:david@;roamware.com] > Sent: Friday, October 18, 2002 11:33 AM > To: Turbine-User > Subject: What are Plexus/Summit? > > > A few people have asked this question and I only found out > myself today by > reading a long thread on the turbine-dev mailing list. I am > glad to see the > full discussion there, it gives me hope. > > To find out about Plexus/Summit see > http://marc.theaimsgroup.com/?l=turbine-dev&m=103474309228654&w=2 and > http://marc.theaimsgroup.com/?l=turbine-dev&m=103477746826521&w=2 and > http://marc.theaimsgroup.com/?l=turbine-dev&m=103483069518535&w=2 and > http://www.apache.org/~jvanzyl/Summit/ > > Read the whole thread for lots of discussion on what should be done. > > My personal take is that folk who are using T3, T2.2 in its > various beta > guises and T2.1 should all plan to move to the latest Turbine > version, which > may possibly be a packaging of Summit if all goes well. The > reasoning behind > this is that the codebase for Fulcrum, Torque and Turbine is > all rather > difficult for the committers to maintain and improve so lets > plan to move > away from it to something cleaner, easier to understand. This > in turn will > allow the same effort to produce more/better Avalon > 'components' of use to > the user community and pluggable into the basic Summit > framework. Apologies > if I have misunderstood some of the classifications of the technology. > > Regards > > David Wynter > > roamware Ltd. > (+44) (0) 208 922 7539 B. > (+44) (0) 7879 605 706 M. > [EMAIL PROTECTED] > > > -- > To unsubscribe, e-mail: > <mailto:turbine-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:turbine-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:turbine-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:turbine-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-user-help@;jakarta.apache.org>
