Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39891 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96100 invoked from network); 12 Aug 2008 16:19:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Aug 2008 16:19:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 89.208.40.236 mail.daylessday.org Linux 2.6 Received: from [89.208.40.236] ([89.208.40.236:35727] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FF/46-04075-308B1A84 for ; Tue, 12 Aug 2008 12:19:15 -0400 Received: from [192.168.3.254] (unknown [212.42.62.198]) by daylessday.org (Postfix) with ESMTP id 7830E640166; Tue, 12 Aug 2008 20:19:12 +0400 (MSD) Message-ID: <48A1B7FD.3050800@daylessday.org> Date: Tue, 12 Aug 2008 20:19:09 +0400 User-Agent: Thunderbird 2.0.0.12 (X11/20071114) MIME-Version: 1.0 To: Lukas Kahwe Smith CC: Marcus Boerger , php-dev 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> <7B8F3FA8-6379-4C78-B004-0034399A7771@pooteeweet.org> In-Reply-To: <7B8F3FA8-6379-4C78-B004-0034399A7771@pooteeweet.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] enabling everything by default From: tony@daylessday.org (Antony Dovgal) On 12.08.2008 20:02, Lukas Kahwe Smith wrote: > 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? No, I didn't expect them to be removed immediately. But what I see now is strong objection against their removal even though there are clear arguments for it. Therefor, I'd expect some kind of plan like "wait for X weeks or till X alpha, then check the number of bugs fixed. If it's still too high -> the extensions are apparently not ready.", or "wait till alphaX, then start voting", or "wait till aplhaX and I'll tell you my decision". > revert previous decisions is not fair to the developer (and the users > waiting for these features). *sigh* That's exactly why I don't think it's going to change whatever I do. "Users waiting for features" will surely beat any common sense. -- Wbr, Antony Dovgal