Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98665
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.19 as permitted sender)
To: Thomas Punt <tpunt@hotmail.co.uk>,
 PHP internals list <internals@lists.php.net>
References: <AM5PR0901MB0930E9A2F1673356429CF5B3F9320@AM5PR0901MB0930.eurprd09.prod.outlook.com>
Message-ID: <86a3be27-e0c0-0e12-2f92-81ca773f0b9f@gmx.de>
Date: Wed, 29 Mar 2017 12:52:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <AM5PR0901MB0930E9A2F1673356429CF5B3F9320@AM5PR0901MB0930.eurprd09.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Bug Reports Targeting Ancient PECL Extensions
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 28.03.2017 at 23:49, Thomas Punt wrote:

> There doesn't appear to be a status quo on what to do with bug reports targeting
> 
> PECL extensions that seem completely unmaintained (i.e. no releases in many years -
> 
> such as bug reports for the SAM extension[1][2]). Would anyone have any objections
> 
> if I closed such reports with a "Won't Fix," given their abandoned status? I know Kalle
> 
> has tagged some of these bug reports with "Suspended," but given the unlikeliness
> 
> of these extensions ever being revived, it seems unnecessary to keep such bug
> 
> reports lying around in the bugs DB.
> 
> 
> Thanks,
> 
> Tom
> 
> 
> [1]: https://pecl.php.net/package/sam
> 
> <https://pecl.php.net/package/sam>
> 
> [2]: https://bugs.php.net/search.php?cmd=display&package_name%5B%5D=sam

See also the related discussion from January:
<http://marc.info/?l=php-internals&w=2&r=2&s=bugsnet+cleanup&q=b>.

-- 
Christoph M. Becker