[development] Go PHP 5, Go!

Gerhard Killesreiter gerhard at killesreiter.de
Mon Jun 11 09:27:17 UTC 2007

Hash: SHA1

Khalid Baheyeldin schrieb:
> On 6/9/07, Konstantin Käfer <kkaefer at gmail.com> wrote:
>> On 07.06.2007, at 04:15, Khalid Baheyeldin wrote:
>> > So, +1 on this initiative. What is the worst case? Come February
>> > and we see that things have not moved. We evaluate it them and see
>> > what other projects did, and decide either to stay the course, or go
>> > back to PHP4.
>> I think this is a bad idea. If we go into this process with this
>> attitude, we won't honestly try to get providers to PHP 5 because
>> there is no need to for them – they will know that software projects
>> won't move to 5 when the majority of providers still run 4. When we
>> really make Drupal (and all the other projects) PHP 5 only starting
>> from this date, providers won't have a choice but to upgrade.
> We don't need to publicize that there is a possibility that we can go
> back in our decision.

Well, you already kind of did.

I think that the first patch that goes in after HEAD will be open for
development again should be one that cleans up some corners of the code
where specific allowance for PHO 4 has been made. (I only know of
drupal_clone, though.)

Then, we could rewrite our RSS generator to use SimpleXML.

If we proceed like this, there will be no way we could revert to support
PHP 4 in February 2008.

I think that the code freeze for Drupal 7 will be some time early next
year. D7 would then be the first release that would make PHP 5.2
mandatory. D8 would then be released late in 2008 or early in 2009. Only
when we release D8, D6 will become unsupported and everybody who wants a
supported Drupal version will actually _have_ to upgrade to PHP 5.2.

I think that having 1.5 years advance warning is plenty and hosters who
dont heed it well deserve to go out of business.

Version: GnuPG v1.4.6 (GNU/Linux)


More information about the development mailing list