> I was hoping that a clearer winner would emerge, but it seems > that people > are all over the place in terms of what they're using. > Anyone have any > ideas as how we should fix this moving forward?
Please, whatever happens, release something that is not Beta, there are lots of customers (including us) that will not touch something until that 4 letter word is removed. With no voting rights, all I can suggest is what I would like to see as a Turbine developer (perhaps we need a poll of what the user's would like to see?): a) 2.1 should be considered End of Life. Expend almost no energy to fixing bugs, but perhaps be nice and friendly and help out anyone with ways to rebuild 2.1 source to fix the issue. (we're using 2.1 so I'm okay with this if (b) follows). b) release 2.2 final in some form. Coupled or not, it's just gotta work. I know our company will not touch 2.2 or anything further until everyone on the Turbine dev team is happy it's no longer Beta. Bloated/Coupled or not, this has to be pretty close to a final release version? c) My gut from reading about it is that Summit/Plexus sounds like a great foundation for a new version of Turbine, so I am interested in what others have to say about Summit (am I right in thinking that "Summit is a kinda-Turbine built on Plexus foundations, which in turn is based on Avalon/Phoenix"?) I love Turbine 2.1, warts and all, but it is pretty big and has a steep learning curve. From the UML diagram of Summit sent on this list, it looks like Summit is much much leaner, and I'm pretty impressed if that UML diagram sent around sums it up, and still provides (most of) the functionality of a Turbine-type-thing. (please correct me if I am way off track here). I applaud the attempts to have a TDK, but perhaps for new versions rather than a TDK, some more thorough docs & Faq's might be easier for the dev team, and more useful in the long run. I'll end this by thanking all the people who have over the time built Turbine what it is today. I'm impressed, and it's helped me a bunch. regards, Paul Smith Lawlex Compliance Solutions phone: +61 3 9278 1151 email: [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-dev-help@;jakarta.apache.org>
