Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42446
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.153 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=oJ7Q5ZSPpiF7ViCsb2SzbylumZtJFvp+NjHkg99ivZWvONHyuffcknOThlWG1jRgsW
         GsyfjuJhgD18vPpP89ALvcD6wUXTloFrCxSWH+L4lNbw8PaAaf/FqzTeZuhQZRdeq7hI
         AlKEHEhrDh+IrG730nSDYKgREqeBC4kWR7Eac=
Message-ID: <fe05d1540901020652x22930f6egf9788bdb0241f9dd@mail.gmail.com>
Date: Fri, 2 Jan 2009 15:52:06 +0100
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: "Marcus Boerger" <helly@php.net>, "George Antoniadis" <george@noodles.gr>, 
	"Timm Friebe" <thekid@thekid.de>, 
	"Stanislav Malyshev" <stas@zend.com>, internals@lists.php.net, 
	"=?ISO-8859-1?Q?\"_\"Johannes_Schl=FCter_\"\"?=" <johannes@php.net>
In-Reply-To: <A8640977-6AEF-47AC-B029-052AE7638AD6@pooteeweet.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <01d401c8fe5e$6bc9d730$16b2a8c0@kartofel>
	 <A5A404F4-2477-44C0-A1CC-EE911FB17BA4@pooteeweet.org>
	 <48EFC1E8.5030702@zend.com>
	 <5D4A905B-E361-409B-BD9E-E816482EDB8C@pooteeweet.org>
	 <4D165E1668394935B126876B72D487CF@carla>
	 <641f88250812311636l7fc8b29x34d4250763cdb903@mail.gmail.com>
	 <49801FDC-2DFD-4A38-AC87-7AE9CBF893B9@pooteeweet.org>
	 <1589625320.20090101145631@marcus-boerger.de>
	 <fe05d1540901010855h159c3208t7e2e70b91cf71867@mail.gmail.com>
	 <A8640977-6AEF-47AC-B029-052AE7638AD6@pooteeweet.org>
Subject: Re: [PHP-DEV] __getStatic
From: pierre.php@gmail.com ("Pierre Joye")

hi,

On Fri, Jan 2, 2009 at 2:59 PM, Lukas Kahwe Smith <mls@pooteeweet.org> wrote:

> @Marcus: Like I said its a question of someone writing the code .. Timm
> proposed a patch which Stas thought had issues and then nobody picked things
> up ..
>
> @Pierre/all: Well we did announce something like a freeze. Of course there
> are still changes going in undiscussed and for the most part this is ok (and
> not doing those changes would be a bad idea and unnecessary to be delayed).
> However I would really appreciate it if people would really think about the
> changes they are doing. Think twice about changes that can introduce a
> regression or a lot of work and ask if the change has any change of being
> problematic.

We all agree here, maybe not being too strict when it comes to
extensions. Breakages in an ext can be reverted at any stage (almost
any).

> In this light the dl() change by Marcus (AFAIK this was planned and done for
> 6.0 and not 5.3) and the windows PCRE change by Andi seem potential
> candidates for regressions, issues and maybe should have been discussed
> beforehand. Just using these two has an example since they are the two last
> commits I marked as potential issues.

If we can't test such changes in the current release phase, then we
will never be able to do anything sane. Alpha releases are mainly
marketing releases, if I can say so. Only very few actually tests them
in comparison to beta or RC.

About the dl issue, I think it is a good idea to drop it in 5.3. It
never worked anyway and causes all kind of side effects (the worst
being segv). However, it would have been preferable to post a little
note on internals before, for the principle :)

> BTW: I was planning on sending out a mail on Monday about beta1. Johannes
> and I feel like a release on the 20th or 22nd seems realistic.


Sounds fine for me too.

Cheers,
-- 
Pierre

http://blog.thepimp.net | http://www.libgd.org