Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44149
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Message-ID: <41E8D342-129D-4182-924C-C1F798FE9619@pooteeweet.org>
To: Andrei Zmievski <andrei@gravitonic.com>,
 PHP Development <internals@lists.php.net>
In-Reply-To: <4A26E286.9010801@gravitonic.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 4 Jun 2009 08:40:08 +0200
References: <4A26E286.9010801@gravitonic.com>
Subject: Re: [PHP-DEV] Notes from the PDM in Chicago
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 03.06.2009, at 22:52, Andrei Zmievski wrote:

> I don't want people here to assume that these notes are "decisions" =20=

> necessarily. They reflect the consensus of the group that was at the =20=

> meeting and we should still take up the unresolved or arguable =20
> issues on this list. But hopefully we have a more structured and =20
> outlined list of things that we can follow for PHP 5.4/6. There are =20=

> a couple of items that were unclear from the original notes =97 =20
> looking at you, Liz Smith :) - so, those of you who remember the =20
> discussion, please fill them in.


To me its absolutely critical that we do not give the impression that =20=

the next bigger update after 5.3 will be 5.4. The next big thing is =20
6.0. If we do a 5.4 then it will come after 6.0, just like 4.4 to ease =20=

migration. But it makes no sense to release 5.4 with forward =20
compatibility stuff until we know we really nailed 6.0.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org