On Thu, 19 Sep 2002 17:19, you wrote:

> >> 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.

While I am happy that the goal is to release Turbine 2.2 ASAP, I really think 
this issue needs to be resolved in such a way that people aren't forced to 
use an unreleased version of the software.  That is exactly why there are so 
many Turbine users/developers out there using their own custom version of 
Turbine 2.1.  I guess I am worried that the same thing will be repeated with 
Turbine 2.2...

> >> 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).

I guess there could be a Turbine 2.21 release (or something like that) that 
allows people to extend turbine-user in a standard way?

Regards,

-- Rodney

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to