"Eric Pugh" <[EMAIL PROTECTED]> writes:
>Hi all,
>I just realized something.. If we are going to start using the fulcrum
>versions of services like Mimetype, pool, etc, don't we need to mark them as
>deprecate ASAP? As in before 2.3 goes out the door? Otherwise we will have
>to maintain them till 2.5 is released? If we mark them deprecated in 2.3,
>then in 2.4 we can start using them. And in 2.5 actually remove the code...
>Is that correct? Am I understanding the rules for deprecation?
Well, I won't deprecate stuff that we might need yet. If the
components plan works out, we deprecate the services in 2.4-dev and
remove them with 2.5-dev.
I see no problem retrofitting an "legacy service broker for Turbine
Services" onto an avalon solution. I don't see it used by default,
though.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
