Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49404
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.187 cause and error)
Message-ID: <4C638727.4090203@lsces.co.uk>
Date: Thu, 12 Aug 2010 06:31:19 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100506 SUSE/2.0.5-1.2 SeaMonkey/2.0.5
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <4C62EC4A.9020106@sugarcrm.com>	<AANLkTikrSSS2YV7h=46KA+QMCLRAGYNPKC_6FOD0sSan@mail.gmail.com>	<4C6320C9.5060306@sugarcrm.com> <AANLkTikw43+dzDFLWmhbouR7Uka-S05uk=pkwwtaqQnj@mail.gmail.com> <4C6324C8.4050700@sugarcrm.com>
In-Reply-To: <4C6324C8.4050700@sugarcrm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] back to 5.4 alpha
From: lester@lsces.co.uk (Lester Caine)

Stas Malyshev wrote:
>
>> I'm totally against an alpha at this stage. Not before we have
>> clarified all we need to get a clean release.
>
> OK, so what do you propose to do? I.e., if you think there are things to
> be discussed, set the agenda. I think that besides typing, trunk is ok
> for alpha, you obvious don't think so. So, in your opinion:
>
> 1. What's missing and should be added?

First thing perhaps ... which IS Pierre's problem ... Windows snapshots
But short of trawling the commit tree ... what HAS already been added?
( links to the CURRENT release notes from the windows site are broken by the way )

> 2. What should be removed?

Without a clean list of what has been added ....
Although I do seem to have missed something in 5.3.3 - where is the constructor 
in a namespaced class if it's not going to use the those that already exist in 
the source non-namespaced one. Not having been able to move TO php5.3 yet I seem 
to have missed that discussion.

> 3. When you expect/want it to happen?

Perhaps some time after PHP5.3 is actually complete on all windows builds?

Creating an Alpha of PHP-Trunk may be a way of creating the documentation that 
is currently missing to even discuss the above questions, but how many of those 
changes have even been tested on windows builds? Perhaps a move to a DVCS 
approach WOULD be a good thing. Nothing gets allowed back into the master 
without the necessary cross checks that there is agreement ... AND it has been 
fully tested across all builds? However I am personally of the opinion that DVCS 
is just creating a much bigger minefield for those projects that now depend on 
it completely :( A single master IS essential for stable production releases.

Currently I am still working my way through the holes in PHP5.3.x which is why 
PHP5.2 is STILL the last stable release as far as my ( windows ) customer sites 
are concerned. SO sensible debate on the next step forward IS more important and 
simply pulling PHP even further apart?

-- 
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//
Firebird - http://www.firebirdsql.org/index.php