RE: RIP PHP 4?

Rasmus Lerdorf

19 years ago

Andi Gutmans wrote:

> I'd suggest something close to what Rasmus suggested:
> a) We make a clear statement on PHP.net that at the end of the year we
> plan to discontinue bug fixes for PHP 4 except for security fixes.
> b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
> and gives people about a year).

The number 8 also has lots of meaning in Chinese culture.  For example
the Beijing Olympics will begin on 8/8/8 at 8:08:08 pm because the word
for 8 sounds like 发 which means prosper or wealth.

-Rasmus

Andi Gutmans

19 years ago

Cool :)

Stanislav Malyshev

19 years ago

> The number 8 also has lots of meaning in Chinese culture.  For example
> the Beijing Olympics will begin on 8/8/8 at 8:08:08 pm because the word
> for 8 sounds like 发 which means prosper or wealth.

Well, then I guess we have no choice but to declare official PHP 4
end-of-life to be on 8:08:08 pm too :) Now we only need to choose a
suitable timezone :)

--
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com

Derick Rethans

19 years ago

On Sun, 8 Jul 2007, Stanislav Malyshev wrote:

> > The number 8 also has lots of meaning in Chinese culture.  For example
> > the Beijing Olympics will begin on 8/8/8 at 8:08:08 pm because the word
> > for 8 sounds like 发 which means prosper or wealth.
>
> Well, then I guess we have no choice but to declare official PHP 4 end-of-life
> to be on 8:08:08 pm too :) Now we only need to choose a suitable timezone :)

GMT+8 of course...

Derick

Alain Williams

19 years ago

On Sun, Jul 08, 2007 at 11:46:08AM +0200, Derick Rethans wrote:

> On Sun, 8 Jul 2007, Stanislav Malyshev wrote:
>
> > > The number 8 also has lots of meaning in Chinese culture.  For example
> > > the Beijing Olympics will begin on 8/8/8 at 8:08:08 pm because the word
> > > for 8 sounds like 发 which means prosper or wealth.
> >
> > Well, then I guess we have no choice but to declare official PHP 4 end-of-life
> > to be on 8:08:08 pm too :) Now we only need to choose a suitable timezone :)
>
> GMT+8 of course...

Which, appropriately enough, includes China.

So: support for PHP4 ends when the Olympics start.

http://upload.wikimedia.org/wikipedia/commons/3/3d/Timezones_optimized.png

--
Alain Williams
Linux Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php
#include <std_disclaimer.h>

Lukas Kahwe Smith

19 years ago

On 08.07.2007, at 16:15, Alain Williams wrote:

> On Sun, Jul 08, 2007 at 11:46:08AM +0200, Derick Rethans wrote:
>> On Sun, 8 Jul 2007, Stanislav Malyshev wrote:
>>
>>>> The number 8 also has lots of meaning in Chinese culture.  For
>>>> example
>>>> the Beijing Olympics will begin on 8/8/8 at 8:08:08 pm because
>>>> the word
>>>> for 8 sounds like 发 which means prosper or wealth.
>>>
>>> Well, then I guess we have no choice but to declare official PHP
>>> 4 end-of-life
>>> to be on 8:08:08 pm too :) Now we only need to choose a suitable
>>> timezone :)
>>
>> GMT+8 of course...
>
> Which, appropriately enough, includes China.
>
> So: support for PHP4 ends when the Olympics start.

one day porting to the next major version of PHP will be olympic ;)

regards,
Lukas

Keryx Web

19 years ago

>> Well, then I guess we have no choice but to declare official PHP 4 end-of-life
>> to be on 8:08:08 pm too :) Now we only need to choose a suitable timezone :)

Well, for us using the 24 hr clock I'd say 8:08:08 am (ante meridiem) as
it otherwise will be 20:08:08 when we speak and write about this event.


Lars Gunther

Rasmus Lerdorf

19 years ago

Keryx Web wrote:

>
>>> Well, then I guess we have no choice but to declare official PHP 4
>>> end-of-life
>>> to be on 8:08:08 pm too :) Now we only need to choose a suitable
>>> timezone :)
>
> Well, for us using the 24 hr clock I'd say 8:08:08 am (ante meridiem) as
> it otherwise will be 20:08:08 when we speak and write about this event.

Except no real geek would schedule anything for 8am.

-R

Tomas Kuliavas

19 years ago

>>>> Well, then I guess we have no choice but to declare official PHP 4
>>>> end-of-life
>>>> to be on 8:08:08 pm too :) Now we only need to choose a suitable
>>>> timezone :)
>>
>> Well, for us using the 24 hr clock I'd say 8:08:08 am (ante meridiem) as
>> it otherwise will be 20:08:08 when we speak and write about this event.
>
> Except no real geek would schedule anything for 8am.

Easy. Schedule it for 8am in China. Do it in Canada, UK or Israel. :)

--
Tomas

David Coallier

19 years ago

On 7/8/07, Tomas Kuliavas <tokul@users.sourceforge.net> wrote:

> >>>> Well, then I guess we have no choice but to declare official PHP 4
> >>>> end-of-life
> >>>> to be on 8:08:08 pm too :) Now we only need to choose a suitable
> >>>> timezone :)
> >>
> >> Well, for us using the 24 hr clock I'd say 8:08:08 am (ante meridiem) as
> >> it otherwise will be 20:08:08 when we speak and write about this event.
> >
> > Except no real geek would schedule anything for 8am.
>
> Easy. Schedule it for 8am in China. Do it in Canada, UK or Israel. :)
>

What about 8/8/8 8pm in china and 01/01/08 Canada, UK, USA.. that way
we can get rid of it quickly and if it's meaningful for chinese people
to use the number 8, we can do it on 8/8/8 for them (irony/joke) ?
Seriously.. I don't really see the point in keeping it for another
year.. imho end of the year is great and more than enough time to
upgrade, we've got to cut the cord sometimes.. why not keep it until
9/9/9 since it's 6/6/6 upside down and means the devil.. the end of
things.. could also be the end of php4

>
> --
> Tomas
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

D

Andi Gutmans

19 years ago

Because some of us don't believe 6 months is enough time for the broad
market to make the move.
One year is more suitable.
As we already stated the message would already be strong today and
people wouldn't wait until the year ends with an end-of-life coming up.
Andi

Tijnema !

19 years ago

On 7/9/07, Andi Gutmans <andi@zend.com> wrote:

> Because some of us don't believe 6 months is enough time for the broad
> market to make the move.
> One year is more suitable.
> As we already stated the message would already be strong today and
> people wouldn't wait until the year ends with an end-of-life coming up.
> Andi

But after PHP4 is dropped, people can still use it, so if people
really need to use it longer then they can just continue using it,
once they are done they can still move on.

Tijnema

>
> > -----Original Message-----
> > From: david.coallier@gmail.com
> > [mailto:david.coallier@gmail.com] On Behalf Of David Coallier
> > Sent: Sunday, July 08, 2007 2:21 PM
> > To: Tomas Kuliavas
> > Cc: internals@lists.php.net
> > Subject: Re: [PHP-DEV] RIP PHP 4?
> >
> > On 7/8/07, Tomas Kuliavas <tokul@users.sourceforge.net> wrote:
> > > >>>> Well, then I guess we have no choice but to declare
> > official PHP
> > > >>>> 4 end-of-life to be on 8:08:08 pm too :) Now we only need to
> > > >>>> choose a suitable timezone :)
> > > >>
> > > >> Well, for us using the 24 hr clock I'd say 8:08:08 am (ante
> > > >> meridiem) as it otherwise will be 20:08:08 when we speak
> > and write about this event.
> > > >
> > > > Except no real geek would schedule anything for 8am.
> > >
> > > Easy. Schedule it for 8am in China. Do it in Canada, UK or
> > Israel. :)
> > >
> >
> > What about 8/8/8 8pm in china and 01/01/08 Canada, UK, USA..
> > that way we can get rid of it quickly and if it's meaningful
> > for chinese people to use the number 8, we can do it on 8/8/8
> > for them (irony/joke) ?
> > Seriously.. I don't really see the point in keeping it for
> > another year.. imho end of the year is great and more than
> > enough time to upgrade, we've got to cut the cord sometimes..
> > why not keep it until
> > 9/9/9 since it's 6/6/6 upside down and means the devil.. the
> > end of things.. could also be the end of php4
> >
> > >
> > > --
> > > Tomas
> > >
> > > --
> > > PHP Internals - PHP Runtime Development Mailing List To
> > unsubscribe,
> > > visit: http://www.php.net/unsub.php
> > >
> > >
> >
> >
> > D
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List To
> > unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--
Vote for PHP Color Coding in Gmail! -> http://gpcc.tijnema.info

Larry Garfield

19 years ago

I have to agree with Andi.  The GoPHP5 effort wanted to have a fairly
aggressive timeline because its main target is projects and shared hosts, and
if it was too far in the future no one would notice.  The involved projects
also won't actually have their next feature release until later in the year
some time.

The PHP dev team, however, has a different set of targets.  It has to include
distros and business servers.  A longer warning period is sensible.

Which of course means that the sooner an EOL date is announced, the sooner PHP
4 can be retired. :-)  Sometime next summer sounds reasonable, and I've no
problem whatsoever with kitch dates[1].

[1] http://gophp5.org/faq#n9

On Sunday 08 July 2007, Andi Gutmans wrote:

> Because some of us don't believe 6 months is enough time for the broad
> market to make the move.
> One year is more suitable.
> As we already stated the message would already be strong today and
> people wouldn't wait until the year ends with an end-of-life coming up.
> Andi
>
> > -----Original Message-----
> > From: david.coallier@gmail.com
> > [mailto:david.coallier@gmail.com] On Behalf Of David Coallier
> > Sent: Sunday, July 08, 2007 2:21 PM
> > To: Tomas Kuliavas
> > Cc: internals@lists.php.net
> > Subject: Re: [PHP-DEV] RIP PHP 4?
> >
> > On 7/8/07, Tomas Kuliavas <tokul@users.sourceforge.net> wrote:
> > > >>>> Well, then I guess we have no choice but to declare
> >
> > official PHP
> >
> > > >>>> 4 end-of-life to be on 8:08:08 pm too :) Now we only need to
> > > >>>> choose a suitable timezone :)
> > > >>
> > > >> Well, for us using the 24 hr clock I'd say 8:08:08 am (ante
> > > >> meridiem) as it otherwise will be 20:08:08 when we speak
> >
> > and write about this event.
> >
> > > > Except no real geek would schedule anything for 8am.
> > >
> > > Easy. Schedule it for 8am in China. Do it in Canada, UK or
> >
> > Israel. :)
> >
> >
> > What about 8/8/8 8pm in china and 01/01/08 Canada, UK, USA..
> > that way we can get rid of it quickly and if it's meaningful
> > for chinese people to use the number 8, we can do it on 8/8/8
> > for them (irony/joke) ?
> > Seriously.. I don't really see the point in keeping it for
> > another year.. imho end of the year is great and more than
> > enough time to upgrade, we've got to cut the cord sometimes..
> > why not keep it until
> > 9/9/9 since it's 6/6/6 upside down and means the devil.. the
> > end of things.. could also be the end of php4
> >
> > > --
> > > Tomas
> > >
> > > --
> > > PHP Internals - PHP Runtime Development Mailing List To
> >
> > unsubscribe,
> >
> > > visit: http://www.php.net/unsub.php
> >
> > D
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List To
> > unsubscribe, visit: http://www.php.net/unsub.php

--
Larry Garfield			AIM: LOLG42
larry@garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an idea,
which an individual may exclusively possess as long as he keeps it to
himself; but the moment it is divulged, it forces itself into the possession
of every one, and the receiver cannot dispossess himself of it."  -- Thomas
Jefferson

chris#

19 years ago

On Sun, 8 Jul 2007 17:21:07 -0400, "David Coallier" <davidc@php.net> wrote:

> On 7/8/07, Tomas Kuliavas <tokul@users.sourceforge.net> wrote:
>> >>>> Well, then I guess we have no choice but to declare official PHP 4
>> >>>> end-of-life
>> >>>> to be on 8:08:08 pm too :) Now we only need to choose a suitable
>> >>>> timezone :)
>> >>
>> >> Well, for us using the 24 hr clock I'd say 8:08:08 am (ante meridiem)
> as
>> >> it otherwise will be 20:08:08 when we speak and write about this
> event.
>> >
>> > Except no real geek would schedule anything for 8am.
>>
>> Easy. Schedule it for 8am in China. Do it in Canada, UK or Israel. :)
>>
>
> What about 8/8/8 8pm in china and 01/01/08 Canada, UK, USA.. that way
> we can get rid of it quickly and if it's meaningful for chinese people
> to use the number 8, we can do it on 8/8/8 for them (irony/joke) ?
> Seriously.. I don't really see the point in keeping it for another
> year.. imho end of the year is great and more than enough time to
> upgrade, we've got to cut the cord sometimes.. why not keep it until
> 9/9/9

Interesting you mention this. Recent studies seem to indicate that the
actual number /is/ 999, and not 666 as everyone believed. They also
believe that it was in reference to Julius Ceaser. But I digress, as I'm
steering this OT. Sorry, just thought I'd mention it.

> since it's 6/6/6 upside down and means the devil.. the end of
> things.. could also be the end of php4
>
>>
>> --
>> Tomas
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>
>
> D
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php

/////////////////////////////////////////////////////
Service provided by hitOmeter.NET internet messaging!
.

Peter Brodersen

19 years ago

On Fri, 06 Jul 2007 22:25:32 -0700, in php.internals
rasmus@lerdorf.com (Rasmus Lerdorf) wrote:

>> b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
>> and gives people about a year).
>
>The number 8 also has lots of meaning in Chinese culture.  For example
>the Beijing Olympics will begin on 8/8/8 at 8:08:08 pm because the word
>for 8 sounds like ? which means prosper or wealth.

A bit more off-topic: A search for Beijing Olympics at Google gives
Reporters sans frontières (Reporters Without Borders), www.rsf.org ,
as one of the first results. If they don't upgrade their PHP 4
installation it would create a great conspiracy theory :)

(of course, sites won't magically go black at that exact moment)


In general I really think every bit of help and information about the
issue would be paramount. Both information about the motive for
discontinuing support and practical information of how to test
existing scripts with PHP 5.

Usually the PHP development does not bother with specific vendors,
products, hosting companies or recommendations in general and so on.
But if we really are up for it, it might have a pacific effect to put
up some "known-good" lists; stuff like "Yes, phpbb does work with
PHP5. Yes, your ISP does support PHP5. Yes, we can recommend tools to
check for basic PHP5 compatibility. Yes, MySQL does work with PHP5".
The hard part about this is that if the lists are just somewhat
non-exhaustive people could be lead to think that all the stuff not
mentioned is not compatible.

php -l  might provide a basic indication of how much havoc an upgrade
will cause. Even though php is downloadable as a shell executable for
Windows as well I think that a bunch of the php developers still using
PHP4 are not into command line administration themselves. Maybe
creating a simple tool (perhaps graphic) to check for the 25 most
common bc breaks as well as lint checks and with detailed information
of what to do.

Basically when we tell users "You can't do that anymore" the obvious
question from the users would be "But what would I have to do
instead?".

I know the development of such a tool might be outside the scope of
usual php development. But if we want to change the behaviour pattern
of the users in the transitional phase it could be necessary.

--
- Peter Brodersen

Larry Garfield

19 years ago

On Monday 09 July 2007, Peter Brodersen wrote:

> Usually the PHP development does not bother with specific vendors,
> products, hosting companies or recommendations in general and so on.
> But if we really are up for it, it might have a pacific effect to put
> up some "known-good" lists; stuff like "Yes, phpbb does work with
> PHP5. Yes, your ISP does support PHP5. Yes, we can recommend tools to
> check for basic PHP5 compatibility. Yes, MySQL does work with PHP5".
> The hard part about this is that if the lists are just somewhat
> non-exhaustive people could be lead to think that all the stuff not
> mentioned is not compatible.

The GoPHP5.org project is part way there, I think. :-)  It's not a "works
with" but a "works only with", but still any project listed there is rather
assumed to be PHP 5-friendly.

I hate to volunteer myself for more work, but is there some way that GoPHP5
could help make that transition easier?  (We can host upgrade guides written
by others too, I suspect.)

--
Larry Garfield			AIM: LOLG42
larry@garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an idea,
which an individual may exclusively possess as long as he keeps it to
himself; but the moment it is divulged, it forces itself into the possession
of every one, and the receiver cannot dispossess himself of it."  -- Thomas
Jefferson

Jani Taskinen

19 years ago

Andi Gutmans wrote:

> I'd suggest something close to what Rasmus suggested:
> a) We make a clear statement on PHP.net that at the end of the year we
> plan to discontinue bug fixes for PHP 4 except for security fixes.
> b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
> and gives people about a year).

Gives a year? Nice. Suddenly we've got some kind of time machine here? :D

It's weird that people think of releases like the thing suddenly vanishes from
all servers it's installed on or it stops working altogether when we're just
saying that we drop support for it. I wish that WAS possible...but unfortunately
people still can install it from existing tar balls..and it will work just fine.

> I also suggest to move PHP 4 downloads to the museum. I suggest though
> to make a clear visible link from php.net/downloads.php to the museum
> and make a clear statement that PHP 4 has moved (I am sure there are
> still many who look for it for application compatibiity reasons).

This to be done immediately?

> A year may seem a long time but it isn't when a company has to port a
> big application over. Also don't forget that one of the reasons so many

Again, the existing installation won't stop working or vanish anywhere on the
date we stop _support_ and don't release new versions of it.. :)

--Jani

Andi Gutmans

19 years ago

See below:

> -----Original Message-----
> From: Jani Taskinen [mailto:jani.taskinen@sci.fi]
> Sent: Saturday, July 07, 2007 6:01 AM
> To: Andi Gutmans
> Cc: PHP Developers Mailing List
> Subject: Re: [PHP-DEV] RIP PHP 4?
>
> Andi Gutmans wrote:
> > I'd suggest something close to what Rasmus suggested:
> > a) We make a clear statement on PHP.net that at the end of
> the year we
> > plan to discontinue bug fixes for PHP 4 except for security fixes.
> > b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds
> > good and gives people about a year).
>
> Gives a year? Nice. Suddenly we've got some kind of time
> machine here? :D
>
> It's weird that people think of releases like the thing
> suddenly vanishes from all servers it's installed on or it
> stops working altogether when we're just saying that we drop
> support for it. I wish that WAS possible...but unfortunately
>   people still can install it from existing tar balls..and it
> will work just fine.

It's not the same. Not giving our users enough heads-up to plan, find
the resources, migrate, test and redeploy is what Microsoft does to its
users (ok so they do give some time but it's always too early and
upgrade path is often much harder). I think we owe it to our users to be
more friendly. For this time period they will require important bug
fixes especially security fixes so I think it ends up being good for
all.
Also don't forget once we make a statement like this, many people will
start planning their migration right away.

>   > I also suggest to move PHP 4 downloads to the museum. I
> suggest though
> > to make a clear visible link from php.net/downloads.php to
> the museum
> > and make a clear statement that PHP 4 has moved (I am sure
> there are
> > still many who look for it for application compatibiity reasons).
>
> This to be done immediately?

Yes, I think we should do this immediately and be sure to make it clear
where to get PHP 4 (clear message with clear visible link). But it will
still "feel" 2nd rate to users.

Andi

Derick Rethans

19 years ago

On Fri, 6 Jul 2007, Andi Gutmans wrote:

> I'd suggest something close to what Rasmus suggested:
> a) We make a clear statement on PHP.net that at the end of the year we
> plan to discontinue bug fixes for PHP 4 except for security fixes.
> b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
> and gives people about a year).
>
> I also suggest to move PHP 4 downloads to the museum. I suggest though
> to make a clear visible link from php.net/downloads.php to the museum
> and make a clear statement that PHP 4 has moved (I am sure there are
> still many who look for it for application compatibiity reasons).

A miracle, it seems like we're even reached consensus on this within a
day :) I'll be preparing the patches to implement this while I'll pass
by here.

And I checked the museum page views, there were 1.2 million of them
since april 20, 2006.

Derick

--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org

Derick Rethans

19 years ago

On Fri, 6 Jul 2007, Andi Gutmans wrote:

> I'd suggest something close to what Rasmus suggested:
> a) We make a clear statement on PHP.net that at the end of the year we
> plan to discontinue bug fixes for PHP 4 except for security fixes.
> b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
> and gives people about a year).

The attached patch mentions the above. As you can see, the idea is to
release this  on the 13th, 3 years after php 5 was released for this
first time.

> I also suggest to move PHP 4 downloads to the museum. I suggest though
> to make a clear visible link from php.net/downloads.php to the museum
> and make a clear statement that PHP 4 has moved (I am sure there are
> still many who look for it for application compatibiity reasons).

I think this is a bit premature - I suggest doing this at the end of the
year as the museum does not have MD5 sums and the like. I did add a
couple of lines in the patch for phpweb to point out this upcoming issue
though on both the downloads and releases pages.

Please have a look at the attached patch and feel free to make any
suggestions towards making the text better.

regards,
Derick

--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org

Pierre Joye

19 years ago

On 7/9/07, Derick Rethans <derick@php.net> wrote:

> On Fri, 6 Jul 2007, Andi Gutmans wrote:
>
> > I'd suggest something close to what Rasmus suggested:
> > a) We make a clear statement on PHP.net that at the end of the year we
> > plan to discontinue bug fixes for PHP 4 except for security fixes.
> > b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
> > and gives people about a year).
>
> The attached patch mentions the above. As you can see, the idea is to
> release this  on the 13th, 3 years after php 5 was released for this
> first time.

First thanks for the patch!

This paragraph is confusing and somehow made my point:

+<p>
+  Hereby the PHP development team announces that support for PHP 4 will
+  continue until the end of this year only. From 2007-12-31 there will be no
+  more releases of PHP 4.4, besides important security releases. Security
+  releases will continue until 2008-08-08 after which PHP 4.4 will no longer be
+  supported officially. Please use the rest of this year to make your
+  application suitable to run on PHP 5.
+</p>


Either we support it or we don't. That means we support it for
security problems only (all non sec bugs reported in php4 will be
bogused or move to php5+ if still present). That also means we will
have security release only until 2008-08-08.

I know that it is what this paragraph says but it could be clearer.
Something like:
- From 2008-01-01, only security fixes will be fixed (btw, there is no
"unimportant" security issue)
- From 2008-08-08, PHP4 is dead, officially and physically

Is there a way to tell something like that in a non confusing way?
There is no need to hide the facts behind some form of kindness :-)

hth

Cheers,
--Pierre

Derick Rethans

19 years ago

On Mon, 9 Jul 2007, Pierre wrote:

> On 7/9/07, Derick Rethans <derick@php.net> wrote:
> > On Fri, 6 Jul 2007, Andi Gutmans wrote:
> >
> > > I'd suggest something close to what Rasmus suggested:
> > > a) We make a clear statement on PHP.net that at the end of the year we
> > > plan to discontinue bug fixes for PHP 4 except for security fixes.
> > > b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
> > > and gives people about a year).
> >
> > The attached patch mentions the above. As you can see, the idea is to
> > release this  on the 13th, 3 years after php 5 was released for this
> > first time.
>
> First thanks for the patch!

I changed the first two paragraphs to:

<p>
Today it is exactly three years ago since PHP 5 has been released. In
those three years it has seen many improvements over PHP 4. PHP 5 is
fast, stable &amp; production-ready and as PHP 6 is on the way, PHP 4
will be discontinued.
</p>
<p>
Hereby the PHP development team announces that support for PHP 4 will
continue until the end of this year only. After 2007-12-31 there will
be no more releases of PHP 4.4. In case security issues might arise after
this date, we will consider making security-only releases up to 2008-08-08.
Please use the rest of this year to make your application suitable to
run on PHP 5.
</p>

I think that reads better.

Derick

chris#

19 years ago

On Tue, 10 Jul 2007 09:34:12 +0200 (CEST), Derick Rethans <derick@php.net> wrote:

> On Mon, 9 Jul 2007, Pierre wrote:
>
>> On 7/9/07, Derick Rethans <derick@php.net> wrote:
>> > On Fri, 6 Jul 2007, Andi Gutmans wrote:
>> >
>> > > I'd suggest something close to what Rasmus suggested:
>> > > a) We make a clear statement on PHP.net that at the end of the year
> we
>> > > plan to discontinue bug fixes for PHP 4 except for security fixes.
>> > > b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds
> good
>> > > and gives people about a year).
>> >
>> > The attached patch mentions the above. As you can see, the idea is to
>> > release this  on the 13th, 3 years after php 5 was released for this
>> > first time.
>>
>> First thanks for the patch!
>
> I changed the first two paragraphs to:
>

No offense, I can't resist...
<p>
Today has been exactly three years since PHP 5 was released. In
those three years it has seen many improvements over PHP 4. PHP 5 is
fast, stable & production-ready and as PHP 6 is on the way, PHP 4
will soon be discontinued.
</p>
<p>
As such, the PHP development team announces that support for PHP 4 will
continue only until the end of this year. After 2007-12-31 there will
be no further releases of PHP 4.4. Except in cases of security issues
that may arise.
Security-only releases will also terminate on 2008-08-08.
We strongly recommend upgrading your applications to PHP 5.
</p>

>
> I think that reads better.

I like this even better. ;)
Thoughts?

>
> Derick
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php

/////////////////////////////////////////////////////
Service provided by hitOmeter.NET internet messaging!
.

Alain Williams

19 years ago

On Tue, Jul 10, 2007 at 01:09:35AM -0700, chris# wrote:

> No offense, I can't resist...

Neither can I:

>  <p>
>    Today has been exactly three years since PHP 5 was released. In
>    those three years it has seen many improvements over PHP 4. PHP 5 is
>    fast, stable & production-ready and as PHP 6 is on the way, PHP 4

s/&/&amp;/

>    will soon be discontinued.
>  </p>
>  <p>
>    As such, the PHP development team announces that support for PHP 4 will
>    continue only until the end of this year. After 2007-12-31 there will
>    be no further releases of PHP 4.4. Except in cases of security issues
>     that may arise.
>    Security-only releases will also terminate on 2008-08-08.
>    We strongly recommend upgrading your applications to PHP 5.
>  </p>
> >

--
Alain Williams
Linux Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php
#include <std_disclaimer.h>

Mark Evans

19 years ago

My 2 cents...

<p>
As of XX-XX-2007, it will have been 3 years since the release of PHP 5. In
these 3 years many improvements have been implemented over PHP 4 and PHP 5
can now be considered fast, stable &amp; production ready. With PHP 6 in
active development PHP 4 development will now be discontinued.
</p>
<p>
Hereby the PHP development team announces that support for PHP 4 will
be discontinued as of 2007-12-31, after this date there will be no more
releases of PHP 4.4. Security issue's found in PHP 4.4 after this date
will be evaluated for severity and the development team will consider
relasing security updates until 2008-08-08.
Please use the rest of this year to make your application suitable to
run on PHP 5.
</p>

Regards

Marco

Andi Gutmans

19 years ago

I wouldn't say "consider" in releasing security fixes. I would say that
we won't make any more releases except in cases of security bugs.

Andi

Pierre Joye

19 years ago

On 7/10/07, Derick Rethans <derick@php.net> wrote:

> On Mon, 9 Jul 2007, Pierre wrote:
>
> > On 7/9/07, Derick Rethans <derick@php.net> wrote:
> > > On Fri, 6 Jul 2007, Andi Gutmans wrote:
> > >
> > > > I'd suggest something close to what Rasmus suggested:
> > > > a) We make a clear statement on PHP.net that at the end of the year we
> > > > plan to discontinue bug fixes for PHP 4 except for security fixes.
> > > > b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
> > > > and gives people about a year).
> > >
> > > The attached patch mentions the above. As you can see, the idea is to
> > > release this  on the 13th, 3 years after php 5 was released for this
> > > first time.
> >
> > First thanks for the patch!
>
> I changed the first two paragraphs to:
>
> <p>
>   Today it is exactly three years ago since PHP 5 has been released. In
>   those three years it has seen many improvements over PHP 4. PHP 5 is
>   fast, stable &amp; production-ready and as PHP 6 is on the way, PHP 4
>   will be discontinued.
> </p>
> <p>
>   Hereby the PHP development team announces that support for PHP 4 will
>   continue until the end of this year only. After 2007-12-31 there will
>   be no more releases of PHP 4.4. In case security issues might arise after
>   this date, we will consider making security-only releases up to 2008-08-08.
>   Please use the rest of this year to make your application suitable to
>   run on PHP 5.
> </p>
>
> I think that reads better.

It is perfect, well done :)

Merci!
--Pierre

Derick Rethans

19 years ago

On Wed, 11 Jul 2007, Pierre wrote:

> On 7/10/07, Derick Rethans <derick@php.net> wrote:
> > On Mon, 9 Jul 2007, Pierre wrote:
> >
> > > On 7/9/07, Derick Rethans <derick@php.net> wrote:
> > > > On Fri, 6 Jul 2007, Andi Gutmans wrote:
> > > >
> > > > > I'd suggest something close to what Rasmus suggested: a) We
> > > > > make a clear statement on PHP.net that at the end of the year
> > > > > we plan to discontinue bug fixes for PHP 4 except for security
> > > > > fixes. b) We will discontinue supporting PHP 4 on 8/8/8
> > > > > (because it sounds good and gives people about a year).
> > > >
> > > > The attached patch mentions the above. As you can see, the idea
> > > > is to release this on the 13th, 3 years after php 5 was released
> > > > for this first time.
> > >
> > > First thanks for the patch!
> >
> > I changed the first two paragraphs to:
> >
> > <p>
> >   Today it is exactly three years ago since PHP 5 has been released. In
> >   those three years it has seen many improvements over PHP 4. PHP 5 is
> >   fast, stable &amp; production-ready and as PHP 6 is on the way, PHP 4
> >   will be discontinued.
> > </p>
> > <p>
> >   Hereby the PHP development team announces that support for PHP 4 will
> >   continue until the end of this year only. After 2007-12-31 there will
> >   be no more releases of PHP 4.4. In case security issues might arise after
> >   this date, we will consider making security-only releases up to 2008-08-08.
> >   Please use the rest of this year to make your application suitable to
> >   run on PHP 5.
> > </p>
> >
> > I think that reads better.
>
> It is perfect, well done :)

Almost, I want to change the 2nd paragraph to:

Hereby the PHP development team announces that support for PHP 4 will
continue until the end of this year only. After 2007-12-31 there will
be no more releases of PHP 4.4. We will continue to make critical security
fixes available on a case-by-case basis until 2008-08-08.  Please use the
rest of this year to make your application suitable to run on PHP 5.

regards,
Derick

Mark Evans

19 years ago

> Almost, I want to change the 2nd paragraph to:
>
>   Hereby the PHP development team announces that support for PHP 4 will
>   continue until the end of this year only. After 2007-12-31 there will
>   be no more releases of PHP 4.4. We will continue to make critical
> security
>   fixes available on a case-by-case basis until 2008-08-08.  Please use
> the
>   rest of this year to make your application suitable to run on PHP 5.

Looks good to me!

Regards

Marco

Anton C. Swartz IV

19 years ago

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.2/894 - Release Date: 7/10/2007 5:44 PM