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.
Huh? Now you're really going to confuse people. You can always have RC2 and more. As it is there will be enough meat to have an RC2 after bug fixes (things which weren't discovered before more people started testing the RC).
We decided on studlyCaps a while ago and I wasn't aware people here didn't apply this decision. Anyway, we are and where in a feature freeze but as I said, I didn't realize people didn't apply that decision. If there's a consensus we can stay with the way things are but I think it's dumb to do so just because an RC has been out for a few days. If we release an RC2 quickly it will be barely noticed. We will regret the inconsistency forever if we don't take care of it (which we already do with the functional part of PHP). If all of you prefer this inconsistency then so be it.
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
