The Zend Framework team announces the immediate availability of Zend Framework 1.10.7, our seventh maintenance release in the 1.10 series. This release includes around 60 bug fixes.
For those uses of Zend_Service_Twitter, please ensure you
upgrade to 1.10.6 or 1.10.7 ASAP. These releases introduce a change in the
Zend_Service_TWitter API that enforces the use of OAuth by
default when using methods that require authentication. The change was
introduced to help prepare Zend Framework users for the Twitter
OAuthcalypse in mid-August. (If you cannot upgrade, there
are other ways to integrate Zend_Oauth with
Zend_Service_Twitter.)
You may download ZF 1.10.7 from the Zend Framework site.
For a full list of resolved issues, you can visit the changelog:
I'd like to thank everyone who contributed code to these releases, including those who submitted patches, translated documentation, or reported issues. Keep your eyes peeled for another maintenance release at the end of next month!
1.11.0 Release Planned
In related news, we are planning a 1.11.0 release for the end of September. This will incorporate bugfixes from the 1.10 series, updates and normalization to validator translation strings, and a variety of new features.
If you have an existing component proposal you would like considered for 1.11.0, please be aware that you will also be required to port it to ZF 2.0; if that does not deter you, please create a proposal ASAP and contact the Community Review Team.
Zend Framework 2.0 Status
We are actively working on ZF 2.0 at this time, and closing in on our first development milestone. In this milestone, we are completing the following tasks:
- Stripping
require_oncecalls from the entire codebase - Refactoring the test suite to use native PHPUnit facilities instead of our hand-written test suites
- Migration to PHP 5.3 namespaces
Once ready, we plan to release a tarball of this milestone, as well as a roadmap showing upcoming milestones on the ZF2 roadmap. Keep tuned for more information in the next couple weeks!
Comments (Login to leave comments)
Also when will zf 2.0 beta or alpha wd be available ??
thx.
ZF2 is in active, but early, development. We will be releasing our first development milestone this week, and hope to have an early alpha available sometime this autumn. The timing of releases is going to be largely dependent on how much time our contributors have to give to the project, as well as how much support we can get for testing from early adopters.
Will the PHP namespace autoloading issues be fixed in version 1.11? (or 1.10.x)
http://framework.zend.com/issues/browse/ZF-8205
http://framework.zend.com/issues/browse/ZF-7907
http://framework.zend.com/issues/browse/ZF-9604
In the ZF 1.X series, we're now at a bit of a crossroads: we need to support vendor prefixes, but there's additional requests for supporting namespaces. With basic autoloading, there's no issues, and we have that working. The problem occurs with plugin loading and resource loading, which typically operate on a vendor prefix => filesystem map. Altering these to support both vendor prefixes and namespaces alike is non-trivial, and can potentially raise some interesting backwards compatibility breaks we'd need to resolve.
That said, we'll be trying to address these issues for 1.11 -- but be aware that we may have to make a stand that ZF1 may only work with vendor prefixes.