Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25877
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fiddy8.com from 64.26.176.17 cause and error)
To: "'Ilia Alshanetsky'" <ilia@prohost.org>,
   "'PHPdev Mailing List'" <internals@lists.php.net>
Date: Thu, 28 Sep 2006 20:30:31 -0400
Message-ID: <000001c6e35e$820c8f50$0301a8c0@mrobinson>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1250"
Content-Transfer-Encoding: 7bit
Thread-Index: AcbjWS8xXQH2kFnZRsySnu4r1iGvXgAA2s0g
In-Reply-To: <9D21C7F4-5269-47C2-B574-F563B378A4CF@prohost.org>
Subject: RE: [PHP-DEV] Filter Vote
From: mike@fiddy8.com ("Mike Robinson")
References: <9D21C7F4-5269-47C2-B574-F563B378A4CF@prohost.org>


On Thursday, September 28, 2006 at  7:52 PM Ilia Alshanetsky wrote:

> A good deal of time has passed and it seems Derick and Pierre 
> are no closer to the consensus about the filter extension and 
> in the meantime 5.2 release process is stalling. At this 
> point I think as the Release Manager I need make a decision 
> on how to proceed. Before I make a decision I'd like to hear 
> some feedback from other developers and users of PHP on what 
> they think.
> 
> The current options are:
> 
> [ ] Indefinitely delay 5.2 release until filter issue can be resolved.
> [ ] Remove filter from PHP 5.2 and hope that some near-future 
> release will re-introduce it [ ] Go with what we have right 
> now, and if filter developers want to make changes they'll 
> need to do so in a manner backwards compatible to the current code.
> 
> Personally, I'd prefer to take filter out entirely from the 5.2 tree.

If the filter extension goes in now and remains marked 'experimental',
making changes that break BC is moot - that's why it's marked experimental
and the docs explain that _very_ clearly - things can and probably will
change.

IMHO, it should go in as is and the 5.2 cycle resumed and completed. If
the guys needed another few days to arrive at a concensus I would consider
that a fair price to pay in order to mitigate BC breaks in the future,
but that additional delay would be at your discretion of course.

Best Regards

Mike Robinson

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.407 / Virus Database: 268.12.9/458 - Release Date: 9/27/2006