Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42050
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain macvicar.net from 193.227.246.108 cause and error)
Message-ID: <492D232D.5090503@macvicar.net>
Date: Wed, 26 Nov 2008 10:21:33 +0000
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Lukas Kahwe Smith <mls@pooteeweet.org>
CC: PHP Internals <internals@lists.php.net>
References: <EB5424AE-8936-4881-A116-A4964ADB2D90@pooteeweet.org> <36F14278-2896-40E1-971C-E488E890EAF7@pooteeweet.org>
In-Reply-To: <36F14278-2896-40E1-971C-E488E890EAF7@pooteeweet.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam_Report: Spam detection software, running on the system "lovelace.midden.org.uk", has
	identified this incoming email as possible spam.  The original message
	has been attached to this so you can view it (if it isn't spam) or label
	similar future email.  If you have any questions, see
	the administrator of that system for details.
	Content preview:  Lukas Kahwe Smith wrote: > > On 22.11.2008, at 14:52, Lukas
	Kahwe Smith wrote: > >> Work is still going on to finalize the namespace
	changes. I am not >> sure when this will be done, I am sort of hoping Monday.
	Then we can >> freeze Tuesday and release on Thursday if all goes well. >
	> > The good news, namespace changes are now finished ahead of alpha3. >
	Documentation is also going to be available soon. > > Now for the bad, I have
	continued the trend of being too optimistic for > the alpha3 release date,
	which is now set for Tuesday December 2nd. > Freeze is therefore on the 28th,
	packaging will happen sometime on > December 1st, allowing a period for important
	last minute fixes as well > as build related work. > > Until then please
	all make sure that you get whatever you can ready. > Since we hope this will
	be our last alpha, it also means that this > release will also mark the end
	for feature additions in self contained > parts of the code. That being said
	I already know of a few items that I > know will not make it into alpha3
	that we might see before beta1. If you > are unsure if your stuff is in this
	mental list, please let me or > Johannes know just to make sure. > > But
	if you have not gotten in contact with one of the RM's about your > stuff
	yet, then its unlikely that we will consider it after beta1. Not > because
	we are mean or because we do not realize that many of you only > have your
	spare time to work on stuff, just because we really really > have to get
	5.3 out the door some day and guess what .. it looks like we > will not even
	have a beta out this year! So think about it .. at least 2 > beta's, 2-4
	RC's and yeah .. it even looks optimistic to go stable in Q1 > 2009. Again
	this is open source, so the only people we do not have to > release on a
	specific date, I just feel bad for all the work people have > put into code
	months ago that is not getting released for so long. > > Anyways, a few items
	from the top of my head that I know people were > talking about: > - rounding
	patch > - stream's [...] 
	Content analysis details:   (-4.3 points, 5.0 required)
	pts rule name              description
	---- ---------------------- --------------------------------------------------
	-1.8 ALL_TRUSTED            Passed through trusted hosts only via SMTP
	-2.6 BAYES_00               BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.1 AWL                    AWL: From: address is in the auto white-list
Subject: Re: [PHP-DEV] apha3
From: scott@macvicar.net (Scott MacVicar)

Lukas Kahwe Smith wrote:
> 
> On 22.11.2008, at 14:52, Lukas Kahwe Smith wrote:
> 
>> Work is still going on to finalize the namespace changes. I am not
>> sure when this will be done, I am sort of hoping Monday. Then we can
>> freeze Tuesday and release on Thursday if all goes well.
> 
> 
> The good news, namespace changes are now finished ahead of alpha3.
> Documentation is also going to be available soon.
> 
> Now for the bad, I have continued the trend of being too optimistic for
> the alpha3 release date, which is now set for Tuesday December 2nd.
> Freeze is therefore on the 28th, packaging will happen sometime on
> December 1st, allowing a period for important last minute fixes as well
> as build related work.
> 
> Until then please all make sure that you get whatever you can ready.
> Since we hope this will be our last alpha, it also means that this
> release will also mark the end for feature additions in self contained
> parts of the code. That being said I already know of a few items that I
> know will not make it into alpha3 that we might see before beta1. If you
> are unsure if your stuff is in this mental list, please let me or
> Johannes know just to make sure.
> 
> But if you have not gotten in contact with one of the RM's about your
> stuff yet, then its unlikely that we will consider it after beta1. Not
> because we are mean or because we do not realize that many of you only
> have your spare time to work on stuff, just because we really really
> have to get 5.3 out the door some day and guess what .. it looks like we
> will not even have a beta out this year! So think about it .. at least 2
> beta's, 2-4 RC's and yeah .. it even looks optimistic to go stable in Q1
> 2009. Again this is open source, so the only people we do not have to
> release on a specific date, I just feel bad for all the work people have
> put into code months ago that is not getting released for so long.
> 
> Anyways, a few items from the top of my head that I know people were
> talking about:
> - rounding patch
> - stream's issues that Greg found and Arnaud recently commented on as
> well as other streams issues
> - openssl patches
> - gd work
> - mysqlnd async stuff ready?
> - interbase ready on windows?
> 
> Independent of that I need someone to handle the move of ext/mhash to PECL.
>

Why not just delete the extension? There isn't anything valuable in
there as it just wraps around hash now, it is literally an empty module
and a configure script.

Scott