Rafael Dohms wrote:
2010/3/11 Johannes Schlüter<johan...@php.net>:
On the other hand merging tests to5.2 and 5.3 means that we can find new
BC breaks we had overseen and either fix them or document them properly.
So I won't "waste" too much time but not forget about 5.2.
As much as I agree with the push for 5.3 adoption, its surely not a
reality with most of the community out
there, like the hosting companies for example.
So like last year i guess we should surely focus on 5.3, but not
discourage any 5.2 work and keep writing
the test for all across, 5.2, 5.3, 6.0
Everyone at our test fest did that, save in cases where the
functionality was not available or altered, the
tests we basically the same for all versions, and i even caught a few
5.2 issues in the process.
I agree in keeping the tests alive for 5.2.
Currently maintaining the 5.2 branch is essential until such time as all
extensions are available in official builds of PHP on windows! Forcing projects
to change their development platforms simply to support a blinkered set of rules
on PHP is not helpful in moving the project forward. How many extensions are
currently stable in 5.2 on windows but not supported in 5.3? Private builds of
the extensions in 5.3 are running without problems .... but having to direct
users to other sites is as bad as the current fragmentation in the core code?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
