4 ms·

https://php.net/migration5 https://php.net/migration5 https://php.net/migration51 https://php.net/migration51 https://php.net/migration52 https://php.net/migrat

https://php.net/migration5 https://php.net/migration5 https://php.net/migration51 https://php.net/migration51 https://php.net/migration52 https://php.net/migration52 https://php.net/migration53 https://php.net/migration53 https://php.net/migration54 https://php.net/migration54 https://php.net/migration55 https://php.net/migration55 https://php.net/migration56 https://php.net/migration56 https://php.net/migration70 https://php.net/migration70 https://php.net/migration71 https://php.net/migration71 https://php.net/migration72 https://php.net/migration72 https://php.net/migration73 https://php.net/migration73 https://php.net/migration74 https://php.net/migration74 (tbd)

ZeroGravitas 7y ago
That's kind of the inverse of what I'd like to see. Similar to browser docs what you're often interetested in is the latest things and how far back you can use them, and where they will degrade gracefully further back. Those mostly assume you have old code that you want to make work on new versions, not that you want to write new code that takes advantage of as much new stuff as possible while still working reasonably well on old versions. It's understandable that they would prefer that everyone just upgrade faster, so it's probably not something they want to encourage (both in documentation and in making features degrade gracefully if that requires any tradeoffs.).