Re: Latest commit -- depreciation of call_user_method()

From: Date: Fri, 18 May 2001 23:16:39 +0000
Subject: Re: Latest commit -- depreciation of call_user_method()
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-55849@lists.php.net to get a copy of this message
[Jani Taskinen <sniper@iki.fi>] > On Thu, 17 May 2001, Rasmus Lerdorf wrote: > > >> I don't agree. Have you noticed the thread about domxml currently running > >> in php-dev@? Wouldn't that justify a 4.1? What would? > > > >No, I don't think a single extension should affect the PHP version number > >to that extent. But I do think we should be moving towards versioning the > >extensions individually. > > Could you explain how having separate version numbers for extensions would > help at all? As long as the extensions are distributed with the main PHP > package, that is. It doesn't help of course. > As long as these extensions are in there, I think changing any of their > API's is a justification for 4.x release. Again, "this is how it's always been done". A single extension has never caused a minor version bump, and I don't see it happening (the only extension I could see remotely justifying that would be ext/standard, which is part of the core anyway...) It is becoming painfully obvious what kind of release nightmare PHP is cornering itself into. The only way out of this mess is to split PHP into smaller projects with their own release cycles, which is what I wanted to do with 4.1 in the first place. Until we do that, we're stuck with our Cathedral, and will continue having RC/QA periods of at least four weeks on micro releases. So MNSHO is that 4.1 should be the split, and nothing but. We can release 4.2 just a couple of months after to address the other things people have signed up for 4.1 now. - Stig -- Stig Sæther Bakken <ssb@fast.no> Fast Search & Transfer ASA, Trondheim, Norway

« previous php.dev (#55849) next »