On 2012-08-02 19:56, Peter Cowburn wrote:
On 2 August 2012 07:35, Adam Harvey <ahar...@php.net> wrote:
Thoughts? (Do we even want to auto-fill this from $OLDRELEASES, or
would we rather have a manual array?) Specific notes on
vulnerabilities to add to branches? Better versions of the copy in the
initial blurb?
Why is this information not just displayed on "Unsupported Historical
Releases" (/releases)? Do you have plans for the EOL page that
wouldn't be suitable for the other one? My worry is spreading this
information across multiple places, when we already have a very
detailed page about unsupported versions. The X.Y version table could
be listed at the top of /releases to give a quick summary, before the
detail for each individual version listed chronologically. We could
add more notes like the existing "Support for PHP 4 has been
discontinued since 2007-12-31." at the appropriate places in that
list.
Just as each release announcement dated with detailed kept on a distinct
page (linked in that list), all that's needed there is a date when
support ended, with (any available) information on what was obsoleted in
the process also on a distinct page - avoid cluttering up the release list.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
