On Fri, 20 Sep 2002 13:25, you wrote: > How about: "The standard way to extend turbine_user in turbine 2.2 is to > use the unreleased fulcrum DBSecurityService (perhaps replaced by Henning's > proposal) in place of the turbine 2.2 integrated DBSecurityService (to do > this you...)." Along with a recommendation that for a production > environment you should keep a copy of the source for the build you are > using so that you can fully support it until the longer term solution is > resolved (which is planned for immediately after the 2.2 release). > > I am trying to be pragmatic about this - my goal is definitely to have a > release that includes the ability to extend turbine-user, but if an interim > step is required that does not fully support this then it is still a step > in the right direction. From your comments I think we are basically in > agreement, but I thought what Mark said adds some good perspective on how > to deal with this type of situation.
Hi Scott, Thanks for your insight. Mark's comments are interesting and they essentially confirm the approach I have been taking up until now. I am quite happy supporting my unreleased version of the Turbine source for the reasons you outlined in your email. Another reason why I would like to see a Turbine 2.2 release is so that we are able to help new Turbine users more effectively, and so that the Turbine 2.x documentation can match the most recently released version. Well, I'm off to India for a couple of weeks, so best of luck everyone. Keep up the good work! -- Rodney -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
