-- till <[EMAIL PROTECTED]> wrote (on Tuesday, 09 December 2008, 12:49 PM +0100): > On Tue, Dec 9, 2008 at 1:07 AM, Sebastian Hopfe <[EMAIL PROTECTED]> wrote: > > Hi till, > > > > i know that this function is added since a long time. This was only an > > example. > > But how i could write a PHPUnit test - so that i get a CodeCoverage by 100% > > and the test is solved complete? > > > > I mean - the ZF is solicited with a 100% Code Coverage. > > > > How this should work at following issue? > > > > http://framework.zend.com/issues/browse/ZF-5091 > > I'd (personally) fix it similar to what you proposed. > > But personally I could also care less about 5.2.4 and see no benefit > in supporting it, let alone making it a requirement. > > Reasons: > > a) It's old -- released in August, 2007. > b) 5.2.5 was released as a security update to 5.2.4. ;-) (Point taken, > a lot of distros backported the fixes.)
We have always recommended using the latest stable PHP release. What we're doing here is specifying the *minimum* PHP version we will support. The rationale behind the decision for 5.2.4 was based on what PHP version is shipped with the linux distributions with greatest market penetration. 5.2.4 is a common baseline, with a few outliers on either other end (some using 5.2.6, others with earlier versions). > I know that for RHEL/CentOS, there are unofficial repositories with an > even more current version of PHP. Understood. However, for users on managed hosting systems, or with RH contracts, usage of unofficial repos will violate terms of service. However, that said, we still upped the minimum supported version. I personally don't feel that advances in PHP should be held hostage by distribution vendors. :) > On Debian there are the unstable and testing branches (most > Debian-people I know recommend unstable even in production). You must know different Debian sysadmins than I do. > Most other distros have no issues offering 5.2.4. And in the end, in > order to be able to stick with maintainable software, you could also > build your own RPM/port/deb/whatever. > > There's really no reason to stick with an old version of PHP. Unless > you run really, really old software but since we are on a Zend > Framework mailinglist, you can rule that out - sort of. ;-) I agree with this in principle. Again, however, we're talking the minimum *supported* version. We cannot simply specify "current stable" as the minimum version, as most institutions will upgrade their server stack much less frequently than their application stack. -- Matthew Weier O'Phinney Software Architect | [EMAIL PROTECTED] Zend Framework | http://framework.zend.com/
