Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37652 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67587 invoked from network); 14 May 2008 16:07:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2008 16:07:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 38.99.98.18 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 38.99.98.18 beast.bluga.net Linux 2.6 Received: from [38.99.98.18] ([38.99.98.18:44237] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3F/AD-31980-22E0B284 for ; Wed, 14 May 2008 12:07:01 -0400 Received: from mail.bluga.net (localhost.localdomain [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id 9DBF5C1043A for ; Wed, 14 May 2008 09:07:00 -0700 (MST) Received: from [192.168.0.106] (CPE-76-84-4-101.neb.res.rr.com [76.84.4.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id 497B3C1040C for ; Wed, 14 May 2008 09:07:00 -0700 (MST) Message-ID: <482B0E1F.1050900@chiaraquartet.net> Date: Wed, 14 May 2008 11:06:55 -0500 User-Agent: Thunderbird 2.0.0.14 (X11/20080502) MIME-Version: 1.0 To: internals Mailing List X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: objection to enabling phar for testing in 5.3? From: greg@chiaraquartet.net (Gregory Beaver) Hi, I wonder if there is any objection to this plan: 1) enable phar by default for the PHP 5.3 betas, so that it can receive full testing 2) before RC1, do the formal vote on whether it should be enabled by default in the release This way, phar can be tested for the possibility of enabling, but there is an explicit safety net in place should it need reconsidering. My assumption here is that there will be a few beta releases and possibly an alpha release or two prior to the first RC. Thanks, Greg