On 8/27/01 12:53 AM, "Jason Grant" <[EMAIL PROTECTED]> wrote:
> Jason's warnings (below) were sobering, so I've not attempted to dabble
> with 3.0 for commercial use.
>
> One month later, do folk recommend that the 3.0 series is still too green
> for general consumption?
Far too green.
> More specifically:
>
> * Is the API still subject to large-scale change/evolution?
Yes. Nothing new has been added to 3.0 yet, we have basically just finished
breaking what was Turbine into Turbine 3.0, Torque, and Fulcrum.
> * The "we can't answer your questions" thing is presumably related to the
> incomplete state of the framework. Have the big hitters been bedded down now?
Not sure what you mean by that.
> * Presumably much of the codebase is inherited from 2.1, so risk of
> bugs/leaks is not likely to be a big issue?
Most of the code has been moved and lot of it just plain removed. Turbine
once was 400+ classes. The core is now at 67 classes.
> * Are the "adapter classes" (below) for backward compatability? If so,
Moving a 2.x app to a 3.x app will require a combination of adapters classes
and some migration scripts. I'm hoping that it won't take much to move the
applications forward. I'm also hoping that the API will remain constant
after 3.0 is released.
> then perhaps the 3.0 stream may be a proposition for *new* products?
I would definitely not use 3.0 for new products at the moment. Definitely
high risk. I work on Tambora and we have production systems that use 2.1
and we won't even think about using 3.0 until it's finished.
> * In general terms, how is the status of 3.0 looking at present - e.g.
> current areas of activity, big areas still requiring work, guestimates of
> timelines, etc.
Like I said, nothing new has been added yet. The API has to be worked out,
the code for pipelines and valves has to go in, and the subapplication
mechansism code has to go in. I have a lot of code (plus some great code
sent to me by Ilkka) but I would like to write the docs first and let people
bash around the ideas first before checking much of it in.
I have no timeline. My primary concern is that a stable API is created so
Sam Ruby can't poke fun at us anymore ;-)
> * Is it correct to assume that the 2.1 branch is considered to be in
> maintenance mode now? i.e. will receive patches, but not enhancement?
Pretty much, I have few code changes that will allow turbine apps to be
tested directly from a CVS layout but it's pretty much bug fixes.
> My motivation here is to assess risk in using the 3.0 stream as a basis
> for a new project.
I would recommend not using it. I don't see how you could start a project
based on something that isn't released. You're just asking for trouble.
> tia
> -j
>
>
> From: Jason van Zyl
> Subject: Turbine 3.0
> Date: Tue, 24 Jul 2001 06:01:15 -0700
>
>
> On 7/24/01 4:02 AM, "Jason Grant" <[EMAIL PROTECTED]> wrote:
>> I'm in the process of upgrading a standalone application to TDK 3.0a3.
>> Is the interim solution to use Turbine.configure(ServletConfig,
>> ServletContext) where TurbineConfig was previously used?
>>
>
> I am going to make this clear now.
> Do not use the 3.0a series unless you know what you're doing. There
> is absolutely no point in upgrading unless you are fully prepared
> to endure some hardship. Scarab has decided to keep up to date with
> the changes and they are helping with the 3.0 development, but 3.0a
> is not a solution for most people. Your apps simply will not work
> right now as the adapter classes will be added later.
>
> Use 3.0a at your own risk. Most questions will not be answered
> and the API will change under your feet so either stop using
> the 3.0a series now and stick to what is stable or prepare to
> help debug and document.
>
> The process for migration will come when we're done 3.0. By all
> means look if want, that's what the 3.0a series is for but we
> can't answer your questions because nothing is final. So again,
> use it at your own peril.
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
