Based on the feedback to the list, I have to change my mind and agree that 2.3 should include pluggable security, not 2.2. I do think it is important to start getting some progress on the version numbers. That way people will know that Turbine is a living viable platform. Should a project be created in Scarab for documentation needs? Then we can add them in, and then work on them. I definitly am availble to do some more documentation.
Eric -----Original Message----- From: Scott Eade [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 3:19 AM To: turbine-user Subject: Re: When will TDK 2.2 be released? > From: Martin Poeschl <[EMAIL PROTECTED]> >> From: Scott Eade [mailto:[EMAIL PROTECTED]] >> >> 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. Okay. Then this means the goal is to release asap. I'm not so sure the torque developers have the same goal in mind as they are happily accepting 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. See above - if torque isn't feature frozen then this cannot happen. > >> 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 Great. >> >> 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 > ... Hmmm. Problem is that I think the only people that have successfully done this have used been using fulcrum. Perhaps the answer is that t2.2 doesn't support this, but if you need to do it then use the unreleased fulcrum. > >> >> 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 ... Cool. Can you please then vote on my proposal over on turbine-dev. > >> 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 I think we should put together a list of the minimum documentation set we need for a 2.2 release so that people can contribute towards this. I am sure there are people willing to contribute in this area. Everyone please offer suggestions here. I will try and put together a review of the existing documentation in the next day or so. > > everyone currently using turbine 2.1 should start moving to 2.2 NOW! and > report all problems, bugs, ... and send patches!! ;-) Agreed, but those that need to extend turbine-user will have to work with fulcrum (where we may incorporate Henning's DBSecurityService proposal). > > martin Thanks for the reply Martin. As far as I can tell your opinion is currently the most critical when it comes to t2.2. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- 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]>
