Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18852 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21011 invoked by uid 1010); 14 Sep 2005 00:23:46 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 20996 invoked from network); 14 Sep 2005 00:23:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Sep 2005 00:23:46 -0000 X-Host-Fingerprint: 64.233.184.200 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.200:20766] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id A4/4B-41173-29D67234 for ; Tue, 13 Sep 2005 20:23:46 -0400 Received: by wproxy.gmail.com with SMTP id i5so67368wra for ; Tue, 13 Sep 2005 17:23:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YRU+vXoriju1P6snEZ4nRTuGKhFpUjg835tRbde3mWV/gebVPgxKTEMM7J5a6MeD14+xvKCO53AZrev2T3JW5clUf6TIkA2OtF5f416yF/zWkjh6uVzfTuULBHRCNpSJ1s/HocmUOmVY1WgiUYhhvm/B/LB6/9SQ+/MRawtvqxc= Received: by 10.54.132.14 with SMTP id f14mr907204wrd; Tue, 13 Sep 2005 17:23:42 -0700 (PDT) Received: by 10.54.154.16 with HTTP; Tue, 13 Sep 2005 17:23:42 -0700 (PDT) Message-ID: Date: Wed, 14 Sep 2005 02:23:42 +0200 Reply-To: pierre.php@gmail.com To: Colin Tucker Cc: Jani Taskinen , internals@lists.php.net In-Reply-To: <43276022.6020702@encode.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43276022.6020702@encode.net.au> Subject: Re: [PHP-DEV] Reference handling change and PHP 4.4.0 From: pierre.php@gmail.com (Pierre Joye) On 9/14/05, Colin Tucker wrote: > Hi Jani, >=20 > Yes, the increase in the middle digit. ;) >=20 > Ok, so does this mean that the 4.3.x and 4.4.x branches will now be > updated separately? Say, if a serious vulnerability was detected in > 4.3.x an 4.4.x, and separate release would be issued for both? No, 4.3.x is a dead branche. But the problem is much more easier to fix in 4.4.0. Do what you always do in production servers, do not display errors/notices, especially as 4.4.0 raises only notices for the reference problem. Regards, --Pierre