-- roberto wrote
(on Tuesday, 05 August 2008, 10:58 AM -0700):
> I dont really know if this is a new topic... but here it goes.
>
>
> With the release of PHP 5.3 alpha1 in the past few days...
>
>
> * Is there any plan to include native namespace support on ZF when 5.3 is
> production ready?
Yes.
> If yes...
> * Any expected release date?
No earlier than mid-2009, and it will be added with version 2.0 of ZF.
> * Is there gonna be a ZF supported branch for 5.1.x - 5.2.x?
> If no...
> * Why not?
We haven't decided yet. I anticipate some issues with maintaining
patches between branches utilizing namespaces and those that do not. If
we are able to create a (somewhat) automated tool for converting
non-namespaced code to namespaced code, I can see no issues with
supporting multiple branches; otherwise, we'll have to carefully
evaluate the efficacy and efficiency of doing so.
> * What do you think of ZF 1.5.x over 5.3? Any breaking changes?
We were alerted of a couple potential issues with naming that we've
corrected as of
1.5.3. I personally have not yet run ZF 1.5.x or ZF
1.6.0 on PHP 5.3alpha1 yet, and likely will not get a chance to until
after the 1.6.0 release. Until then, anybody who has, please post your
experiences here.
> * What do you think of the migration of "current non-namespaced
> applications / components / frameworks" built over "current non-namespaced
> ZF" to a "future namespaced ZF"?
We aim to provide a way to translate non-namespaced classes to
namespaced versions. Implementation is still in the air -- the features
have just recently frozen, so doing much before this has been low
priority.
> I really want to know the future of ZF... because...
>
> Most of us have invested a lot of time building components over ZF.
> Most of us want to know what is gonna change for the current applications.
> Most of us want to use state-of-the-art technologies that make our life
> easier and a little bit more organized.
> Most of us want to know if we have to spend time in the future refactoring
> or migrating applications.
My aim is to have migration tools available for 2.0 to help you migrate
your code to use namespaces. I can almost guarantee that any such
tooling will still require manual intervention -- but hopefully this can
be mitigated with good documentation of the migration process.
_YOU_ can help with this planning as we start gearing up for 5.3
support, and I'll be keeping the lists posted with current efforts and
areas where assistance could be utilized.
--
Matthew Weier O'Phinney
Partager