Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19306 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36023 invoked by uid 1010); 30 Sep 2005 13:02:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 36008 invoked from network); 30 Sep 2005 13:02:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Sep 2005 13:02:25 -0000 X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:49816] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 7C/D6-54476-0673D334 for ; Fri, 30 Sep 2005 09:02:25 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j8UD2JRm015197; Fri, 30 Sep 2005 15:02:19 +0200 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j8UD2DIR015179; Fri, 30 Sep 2005 15:02:15 +0200 Date: Fri, 30 Sep 2005 15:02:13 +0200 (CEST) X-X-Sender: derick@localhost To: Wez Furlong cc: Andi Gutmans , internals@lists.php.net In-Reply-To: <4e89b4260509300553r7581a563u2a580c4106a341d5@mail.gmail.com> Message-ID: References: <433ABE48.6050607@lerdorf.com> <6.2.3.4.2.20050928155517.04710860@localhost> <6.2.3.4.2.20050929073711.0453cd30@localhost> <4e89b4260509300553r7581a563u2a580c4106a341d5@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at jdi-ict.nl Subject: Re: [PHP-DEV] timezones & date() breakage From: derick@php.net (Derick Rethans) On Fri, 30 Sep 2005, Wez Furlong wrote: > 20 known (and worked-around) bugs are "better" than an unknown > quantity of unknown bugs. > > Remember: it worked "yesterday" but with the minor release it stops working. > Just because the new version works for you, doesn't mean it isn't > broken for others :) > > Can you honestly guarantee that it's not going to be a BC break by the > time we release? Well, it would be much better if we just force people to set the setting correctly, then it doesn't break any BC. And ofcourse, you can never guarantee anything for a 100%, but it definitely should cover things for a large majority. I do think we should not be saying "oooh, it doesn't work - let's remove it and go back to "working" code, which is broken. Also, if it *does* gets guessed wrong, all you need to do is set one php.ini setting. If this was a .0.x release then this is a problem, but not when you're bumping from 5.0 to 5.1. regards, Derick