Re: [RFC] orphan extensions cleanup
| From: | Kalle Sommer Nielsen | Date: | Mon, 15 Aug 2016 17:02:28 +0000 |
| Subject: | Re: [RFC] orphan extensions cleanup | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95196@lists.php.net to get a copy of this message | ||
2016-08-15 18:05 GMT+02:00 Lester Caine <lester@lsces.co.uk>:
> Don't go there again!
If there is no active maintainer, it just creates a burden on us core
developers that have to maintain it to the best of our abilities if
any, but there have not been anyone to take over the charge of this
extension, so unless someone does now, I do not see a reason to keep
this in the core. I understand that there are users of this extension,
but we cannot guarantee it to be in any sort of stable working
condition if there isn't anyone around to work on it.
Alternatively we still have ext/pdo_firebird, which I assume will
continue to work with Interbase systems. If not then I'm sorry, but I
do not want another extension on our checklist if no one is willing to
work on it.
Same issue for ext/mssql, although in MSSQL's case we do have
ext/pdo_dblib (pdo_mssql), ext/odbc & ext/pdo_odbc as an alternative.
If there is someone who can actively work on it, then it can have PECL
releases and if there is a big demand for it, I do not see why it
cannot return to the core at a point in time it is well maintained
(either extension that is)
--
regards,
Kalle Sommer Nielsen
kalle@php.net