Given that someone commented that decoupling Turbine 2.2 would be a lot like what Turbine 3.0 is, what if Turbine 3.0 was released soon? Instead of taking the time to get the decoupled Turbine 2.x released, use it to ready Turbine 3.0 for release.
I'm not quite up to speed on release cycles and the state of the code base and what not, so this may not be a good suggestion, but I've been using Turbine 3 for an app that's in development and it's been going well. - Stephen > -----Original Message----- > From: Martin Poeschl [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 04, 2002 11:45 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: [proposal] kill the coupled torque and services > > the coupled versions of torque and fulcrum (service stuff) are not maintained any > longer. > we told the users to use the decoupled versions ... good idea, but it doesn't work :-( > > many people waste there time trying to make them work together, so i propose to kill > the coupled > versions and use the decoupled for turbine 2.x > > we could release turbine 2.2 including the coupled versions and kill them for 2.3 > > this will stop people to start with the old code and will make switching to turbine 3 > easier for them. > > i crosspost this mail, to give the users a chance to comment the plan ;-) > > martin > > > > -- > 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]>
