Kris Craig wrote:
I'm probably missing something, but why not just do it like we did with
5.2? I.e. we keep maintaining it until PHP 5.5, at which time we deprecate
it and be done with it?
Like I said, I'm probably missing something lol, so if someone could
explain why this is different I'd be much obliged! =)
Certainly I can see many people who have only just finally updated thing to work
on PHP5.3 might well skip 5.4 and then look to another update when 5.5 comes
out. Stopping security updates on 5.3 and then not providing 5.5 for another
couple of months while not particularly problematic does seem to be a little
irritating, but a fixed timetable that should provide an overlap would be ideal
... with the flexibility to move the deadline if there IS some major reason that
5.5 has not been released as currently planned?
--
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
