Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:8709
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Tue, 23 Mar 2004 13:24:05 -0800 (PST)
To: Georg Richter <georg@php.net>
cc: john@coggeshall.org, George Schlossnagle <george@omniti.com>,
        Edin Kadribasic <edink@emini.dk>, Marcus Boerger <helly@php.net>,
        PHP Internals <internals@lists.php.net>
In-Reply-To: <200403232219.18491.georg@php.net>
Message-ID: <Pine.LNX.4.58.0403231321300.1376@thinkpad.lerdorf.com>
References: <1079935882.5524.0.camel@coogle.localdomain> <200403231858.57603.georg@php.net>
 <1080072351.14294.6.camel@coogle.localdomain> <200403232219.18491.georg@php.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Studlycaps and MySQLi
From: rasmus@php.net (Rasmus Lerdorf)

On Tue, 23 Mar 2004, Georg Richter wrote:
> Changing everything after an announced feature freeze sucks. It's just  
> ignoring others (users, authors and publishers) - a loss of face. Obviously 
> some people like this kind of policy - me not!

I do agree with this.  There is no point in announcing a freeze if you
turn around and change a bunch of fundamental things the next day.  If we
are really going to go back and change all these method names then I think
the correct way to do it is to pull RC1 and let people know that we
discovered some things that need to be cleaned up and we will attempt
another freeze and RC1 at a later date.

-Rasmus