On Do, Jul 29, 2010 at 10:28:32 -0400, Matthew Weier O'Phinney wrote: > It's actually somewhat hard to answer that question at this time. > > We're preparing to release our first development milestone of ZF2, which > has accomplished the following: > > * Stripping of require_once calls > * Conversion to namespaces (except for some Zend_Service components) > * Updates to the test suite (removed all AllTests classes in favor of > using native PHPUnit functionality) > * Rewrite of Zend\Session (required so that we could actually test it > post-migration; it's been entirely re-architected) > > Ralph is building a sample app currently so that we have a baseline > against which we can do some performance profiling. He's discovered that > despite passing tests in individual components, the MVC is not fully > functional currently. He is investigating, and hoping to get it working > soon. > > However, this is just the first milestone. Refactoring begins in earnest > after this point, so the APIs will be very unstable for a matter of some > months at the least. I'm not sure if we'll have a stable release ready > in the January/February timeline or not; much of it will be dependent on > how much mindshare and time we can get from our own contributor > community as we move into a more active ZF2 development phase. > > Personally, if your project is intended to be production stable for the > timeframe you indicate, I'd go with ZF1, and plan a later iteration > of the project to migrate to ZF2. > Okay, it is to be feared that we must go with the zf1 and migrate later to the zf2 code base ;-)
Thank you for the answer. Mario
