Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39888 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91093 invoked from network); 12 Aug 2008 16:04:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Aug 2008 16:04:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:38158] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 05/45-04075-084B1A84 for ; Tue, 12 Aug 2008 12:04:17 -0400 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id DBF1C4144007; Tue, 12 Aug 2008 16:05:57 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id obnryywnh+1F; Tue, 12 Aug 2008 18:05:57 +0200 (CEST) Received: from [172.25.51.165] (tmo-113-2.customers.d1-online.com [80.187.113.2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id B79204144006; Tue, 12 Aug 2008 18:05:54 +0200 (CEST) Cc: Marcus Boerger , php-dev Message-ID: <7B8F3FA8-6379-4C78-B004-0034399A7771@pooteeweet.org> To: Antony Dovgal In-Reply-To: <48A1B221.9030109@daylessday.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v928.1) Date: Tue, 12 Aug 2008 18:02:07 +0200 References: <4892E15D.1080004@daylessday.org> <48A19D61.6080502@daylessday.org> <1461769324.20080812165923@marcus-boerger.de> <48A1A6A4.1050801@daylessday.org> <1257013106.20080812172357@marcus-boerger.de> <48A1ACBC.7020808@daylessday.org> <48A1B221.9030109@daylessday.org> X-Mailer: Apple Mail (2.928.1) Subject: Re: [PHP-DEV] enabling everything by default From: mls@pooteeweet.org (Lukas Kahwe Smith) On 12.08.2008, at 17:54, Antony Dovgal wrote: > On 12.08.2008 19:35, Lukas Kahwe Smith wrote: >> If we, the RMs, see that these extensions are not yet ready, we >> will not hesitate to pull any of them. We will make such a >> decision before we go into the RC phase. Until then it would be >> only fair to not push the developers in question into such a >> defensive corner. They should spend their open source brain cycles >> on fixing bugs not in this thread. > > The point is that I don't see any results of this thread. Or rather > the results are quite indefinite. What result are you expecting? That they are removed immediately? That all bugs are instantly fixed? That the previous decisions of enabling by default of these extensions is revoked in light of bugs being found in the alpha phase of 5.3? This would be unreasonable. What is reasonable is that it has been acknowledged that several of the newly added and enabled by default extensions have issues. And the reassurance that if these bugs do not get resolved these extensions might not be enabled by default or not even bundled to begin with. Nobody is saying "Tony do not mention issues in new extensions". But pointing to bugs in code that is part of alpha releases (or to make it even clearer non RC/stable releases) and saying this is enough to revert previous decisions is not fair to the developer (and the users waiting for these features). regards, Lukas Kahwe Smith mls@pooteeweet.org