We just recently upgraded from 2.1 to 2.2 with decoupled Torque. Most (if not all) the changes were associated with the newer Torque (Criteria, List etc) classes which were found during compilation.
1. Regenerate OM tree using new Torque 2. Change package names for use with new Torque; ie Criteria, Numberkey etc 3. Change Vector returns from Peer to List 4. Recompile. Any other problems will be detected. That's about it /colin First off, I would like to thank the small-ish number of people who are keeping the Turbine framework moving forward, for a while there I thought a highly targetted missile had taken out the Turbine team.... I (and I am sure everyone else) appreciate the amount of time you are all dedicating to it, I know it's not a trivial undertaking with jobs/wives etc. Could someone in the know provide a "Top 10 things you'd have to do to migrate from 2.1 -> 2.2", not looking for too much detail, just a one liner per item. e.g. "Change any reference to package A to reference package B", or "Replace all those Vector's in the BasePeer stuff with the List interface". I just want to get a feel the amount of effort involved. We've just come off implementing a pretty large 2.1 project, and it's working sooooo well, I don't want to rock the boat. Actually, everyone seems to say "the bug fixes in 2.2 are reason enough". Yeah? What bugs were people pulling their hair out over in 2.1? (maybe we just never used that portion). regards, Paul Smith -----Original Message----- From: Martin Poeschl [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 5:00 PM To: Turbine Users List Subject: Re: When will TDK 2.2 be released? [EMAIL PROTECTED] wrote: > I definitly agree that having a working extend user is crucial for 2.2. The > other one I would toss out (although the scope might be too much) is to > integrate the new Security schemes that have been tossed out. > > I think doing those two things would give people a reason to upgrade to 2.2, > versus staying with 2.1. Right now, while the decoupled stuff is cool, it > adds more complexity as well. And doesn't seem to be a compelling reason to > upgrade. Fixing the extend user abilty and pluggable security do seem > compelling. > > Eric > > -----Original Message----- > From: Scott Eade [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 18, 2002 7:25 AM > To: turbine-user > Subject: Re: When will TDK 2.2 be released? > > > >>From: Martin Poeschl <[EMAIL PROTECTED]> >> >>there is no release date planned :-( >>but you should definitly start with 2.2 and report any problems!! >> >>2.2 works fine for my apps, but we need more testing before a final > > release > >>martin > > > Martin, > > Surely there must be some kind of features based target for a 2.2 release, > otherwise there will only ever be 2.2 beta releases until the end of time. there will be no major changes before the final release of turbine 2.2 basically there should only be bug-fixes and doc enhancements. > > I think we need to come up with a list of requirements that need to be met > in order to declare a turbine/tdk 2.2 final release. I would imagine this > list might include: > > 1. A release of torque 3.0 final (we need to start the same discussion on > the torque-dev list with respect to torque). torque 3.0 and turbine 2.2 will be release together. > 2. A release of maven 1.0 final (I would imagine the maven guys have some > fairly specific criteria in mind for their 1.0 release). i don't think we have to wait for a 1.0 release ... the final verisions will be built with the latest maven release > > I would like to add my personal bugbear to the list: > > 3. A working, documented solution to the requirement to extend the > turbine_user table. +1 i never had to extend the turbine user table .. so i need some feedback here ... > > Surely there is room for a process here? Why can't the committers and users > of turbine nominate the requirements for a 2.2 final release (features, > fixes, issues, etc.) These can be voted upon individually and the accepted > ones added into the todo page on the turbine-2 site. This would provide > something for the contributors to work towards and a better answer to the > "when will turbine 2.2 be released?" question than "nothing is planned". scarab is working fine for torque now .. we should also use it for turbine .. so all request should go to the bugtracking system ... > What do you believe are the things that need to be done before a turbine/tdk > 2.2 final release can be realized? the current docs are not as usefull as they should be we need more people testing the current builds everyone currently using turbine 2.1 should start moving to 2.2 NOW! and report all problems, bugs, ... and send patches!! ;-) 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
