It is approaching 2 1/2 years since the last release of PHP 5.2. 5.2
has been declared dead on more than one occasion around here. The dust
has more or less settled since PHP 5.3 EOL was announced. The ONLY
reason I still support 5.2 in my own userland software is because the
5.2 binaries are available on windows.php.net. There are some things
I'd like to do that are only available in the core in 5.3 and later but
I won't do them until the binaries for 5.2 disappear from the website.
I like to make sure I reach the widest possible, yet rationally
supportable audience. As such, I figure that generally supporting
whatever users can download from an official source is a good logical
cutoff point.
Is the issue the 5.2 binaries haven't been retired due to 5.2 being
compiled with VC6? VC10 and VC11 runtimes fixed a lot of the issues
that the VC8 and VC9 runtimes had. I've dropped VC11 runtimes into the
same directory as the PHP 5.5 binaries and they seem to work fine on
hosts without VC11 on them. That is a huge improvement over the VC9
runtimes, which are a nightmare to work with from both a development and
deployment perspective.
What I'm NOT saying is that the 5.2 binaries should come down right now.
What I am saying is that the discussion and the plan formulated for
their removal should take place if it hasn't already.
--
Thomas Hruska
CubicleSoft President
I've got great, time saving software that you might find useful.
On Mon, Sep 2, 2013 at 10:38 AM, Thomas Hruska thruska@cubiclesoft.comwrote:
It is approaching 2 1/2 years since the last release of PHP 5.2. 5.2 has
been declared dead on more than one occasion around here. The dust has
more or less settled since PHP 5.3 EOL was announced. The ONLY reason I
still support 5.2 in my own userland software is because the 5.2 binaries
are available on windows.php.net. There are some things I'd like to do
that are only available in the core in 5.3 and later but I won't do them
until the binaries for 5.2 disappear from the website. I like to make sure
I reach the widest possible, yet rationally supportable audience. As such,
I figure that generally supporting whatever users can download from an
official source is a good logical cutoff point.Is the issue the 5.2 binaries haven't been retired due to 5.2 being
compiled with VC6? VC10 and VC11 runtimes fixed a lot of the issues that
the VC8 and VC9 runtimes had. I've dropped VC11 runtimes into the same
directory as the PHP 5.5 binaries and they seem to work fine on hosts
without VC11 on them. That is a huge improvement over the VC9 runtimes,
which are a nightmare to work with from both a development and deployment
perspective.What I'm NOT saying is that the 5.2 binaries should come down right now.
What I am saying is that the discussion and the plan formulated for their
removal should take place if it hasn't already.
Currently the downloads page on http://php.net/ only lists the supported
versions(5.3, 5.4, 5.5) and I think that http://windows.php.net/ should be
synced with that, so the 5.2 links should be removed.
http://museum.php.net/ already has those binaries, so it would be still
available for those who are looking for that version, but without the
possible confusion that the 5.2 version is still supported on windows.
Pierre, what do you think?
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
hi,
On Mon, Sep 2, 2013 at 10:38 AM, Thomas Hruska thruska@cubiclesoft.comwrote:
It is approaching 2 1/2 years since the last release of PHP 5.2. 5.2 has
been declared dead on more than one occasion around here. The dust has
more or less settled since PHP 5.3 EOL was announced. The ONLY reason I
still support 5.2 in my own userland software is because the 5.2 binaries
are available on windows.php.net. There are some things I'd like to do
that are only available in the core in 5.3 and later but I won't do them
until the binaries for 5.2 disappear from the website. I like to make sure
I reach the widest possible, yet rationally supportable audience. As such,
I figure that generally supporting whatever users can download from an
official source is a good logical cutoff point.Is the issue the 5.2 binaries haven't been retired due to 5.2 being
compiled with VC6? VC10 and VC11 runtimes fixed a lot of the issues that
the VC8 and VC9 runtimes had. I've dropped VC11 runtimes into the same
directory as the PHP 5.5 binaries and they seem to work fine on hosts
without VC11 on them. That is a huge improvement over the VC9 runtimes,
which are a nightmare to work with from both a development and deployment
perspective.What I'm NOT saying is that the 5.2 binaries should come down right now.
What I am saying is that the discussion and the plan formulated for their
removal should take place if it hasn't already.Currently the downloads page on http://php.net/ only lists the supported
versions(5.3, 5.4, 5.5) and I think that http://windows.php.net/ should be
synced with that, so the 5.2 links should be removed.
http://museum.php.net/ already has those binaries, so it would be still
available for those who are looking for that version, but without the
possible confusion that the 5.2 version is still supported on windows.
Pierre, what do you think?
There is no link from windows.php.net web sites to 5.2. They only
remain in the downloads section, if accessed directly.
Cheers,
Pierre
@pierrejoye | http://www.libgd.org
Pierre Joye wrote:
There is no link from windows.php.net web sites to 5.2. They only
remain in the downloads section, if accessed directly.
I think it's the presence of 5.2 on the download page that is being talked
about? While I still have reason to use 5.2, I'd support dropping this ti the
archives. You only need to be using 5.2 if you already have it installed, and
it's up to us to manage that access.
--
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
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
Currently the downloads page on http://php.net/ only lists the supported
versions(5.3, 5.4, 5.5) and I think that http://windows.php.net/ should
be
synced with that, so the 5.2 links should be removed.
http://museum.php.net/ already has those binaries, so it would be still
available for those who are looking for that version, but without the
possible confusion that the 5.2 version is still supported on windows.
Pierre, what do you think?There is no link from windows.php.net web sites to 5.2. They only
remain in the downloads section, if accessed directly.
yes, we are talking about the downloads page, which page is linked from
like every release annonuncement on the windows.php.net frontpage(we even
have 5.2 release announcements if you scroll down a bit).
I think we should remove the 5.2 section from the downloads page.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Currently the downloads page on http://php.net/ only lists the
supported
versions(5.3, 5.4, 5.5) and I think that http://windows.php.net/should
be
synced with that, so the 5.2 links should be removed.
http://museum.php.net/ already has those binaries, so it would be
still
available for those who are looking for that version, but without the
possible confusion that the 5.2 version is still supported on windows.
Pierre, what do you think?There is no link from windows.php.net web sites to 5.2. They only
remain in the downloads section, if accessed directly.yes, we are talking about the downloads page, which page is linked from
like every release annonuncement on the windows.php.net frontpage(we even
have 5.2 release announcements if you scroll down a bit).
I think we should remove the 5.2 section from the downloads page.
I agree as it's been EOLed.
Julien.Pauli
done, was sure it was done since long already.
Currently the downloads page on http://php.net/ only lists the
supported
versions(5.3, 5.4, 5.5) and I think that http://windows.php.net/
should
be
synced with that, so the 5.2 links should be removed.
http://museum.php.net/ already has those binaries, so it would be
still
available for those who are looking for that version, but without the
possible confusion that the 5.2 version is still supported on windows.
Pierre, what do you think?There is no link from windows.php.net web sites to 5.2. They only
remain in the downloads section, if accessed directly.yes, we are talking about the downloads page, which page is linked from
like every release annonuncement on the windows.php.net frontpage(we even
have 5.2 release announcements if you scroll down a bit).
I think we should remove the 5.2 section from the downloads page.I agree as it's been EOLed.
Julien.Pauli
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
Pierre Joye wrote:
done, was sure it was done since long already.
Pierre ... I think that the 5.2 stuff was left as the only VC6 build. The notes
of the side bar refer still to using that when perhaps a 'no longer supported'
may be better?
--
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
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
Pierre Joye wrote:
done, was sure it was done since long already.
Pierre ... I think that the 5.2 stuff was left as the only VC6 build. The
notes of the side bar refer still to using that when perhaps a 'no longer
supported' may be better?
As it is no longer supported it has no place there.
However you can still fetch it here http://windows.php.net/downloads/
we keep there as many installers fetch it from there, as convenience.
But its time is counted as well (will be moved to museum),
--
Pierre
@pierrejoye | http://www.libgd.org
Pierre Joye wrote:
Pierre Joye wrote:
done, was sure it was done since long already.
Pierre ... I think that the 5.2 stuff was left as the only VC6 build. The
notes of the side bar refer still to using that when perhaps a 'no longer
supported' may be better?As it is no longer supported it has no place there.
However you can still fetch it here http://windows.php.net/downloads/
we keep there as many installers fetch it from there, as convenience.
But its time is counted as well (will be moved to museum),
Pierre ... all I am saying is that the reference to 'older VC6 versions' in the
left hand column would benefit from a 'which are only available in the museum',
although I would suggest it may be better simply to say 'no longer supported'.
I seem to recall that you did take the 5.2 stuff off, but restored it when the
Apache link was pointed out ... but I may well be wrong ;)
--
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
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
Pierre ... all I am saying is that the reference to 'older VC6 versions' in
the left hand column would benefit from a 'which are only available in the
museum', although I would suggest it may be better simply to say 'no longer
supported'.
I do not think it would benefit anyone to promote VC6, in any form :)
The only note we keep there is about using apache.org's binaries:
"If you are using PHP with Apache 1 or Apache2 fromapache.org (not
recommended) you need to use the older VC6 versions of PHP compiled
with the legacy Visual Studio 6 compiler. Do NOT use VC9+ versions of
PHP with the apache.org binaries."
Cheers,
Pierre
@pierrejoye | http://www.libgd.org
Pierre Joye wrote:
Pierre ... all I am saying is that the reference to 'older VC6 versions' in
the left hand column would benefit from a 'which are only available in the
museum', although I would suggest it may be better simply to say 'no longer
supported'.I do not think it would benefit anyone to promote VC6, in any form :)
Exactly
The only note we keep there is about using apache.org's binaries:
"If you are using PHP with Apache 1 or Apache2 fromapache.org (not
recommended) you need to use the older VC6 versions of PHP compiled
with the legacy Visual Studio 6 compiler. Do NOT use VC9+ versions of
PHP with the apache.org binaries."
Which is why I said 'no longer supported' so an extra line
"This is no longer supported." Would just clarify the situation rather than it's
current suggestion that you SHOULD use the VC6 versions ...
--
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
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
Pierre Joye wrote:
Pierre ... all I am saying is that the reference to 'older VC6 versions'
in
the left hand column would benefit from a 'which are only available in
the
museum', although I would suggest it may be better simply to say 'no
longer
supported'.I do not think it would benefit anyone to promote VC6, in any form :)
Exactly
The only note we keep there is about using apache.org's binaries:
"If you are using PHP with Apache 1 or Apache2 fromapache.org (not
recommended) you need to use the older VC6 versions of PHP compiled
with the legacy Visual Studio 6 compiler. Do NOT use VC9+ versions of
PHP with the apache.org binaries."Which is why I said 'no longer supported' so an extra line
"This is no longer supported." Would just clarify the situation rather than
it's current suggestion that you SHOULD use the VC6 versions ...
And it is what it means, you must use VC6, not supported anymore, if
you use apache.org's binary.
--
Pierre
@pierrejoye | http://www.libgd.org