On 29.06.2019 at 18:31, Peter Kokot wrote: > On Fri, 28 Jun 2019 at 17:57, Christoph M. Becker <cmbecke...@gmx.de> wrote: >> >> On 28.06.2019 at 17:49, Peter Kokot wrote: >> >>> On Thu, 10 Jan 2019 at 19:43, Stanislav Malyshev <smalys...@gmail.com> >>> wrote: >>>> >>>>> ext/imap should follow the same road. >>>>> >>>>> BTW, if we want to keep this extension, we need to consider the bundled >>>>> library as a fork, maintained by US (and drop support to build using the >>>>> system library, if present) >>>>> >>>>> So, any new volunteer to maintain this extension, will also have to >>>>> maintain the library. >>>> >>>> This looks unlikely, so we shouldn't count on it happening. I think we >>>> should just move them to PECL and if somebody shows up, we can always >>>> move it back. >>> >>> Hello, sorry for bumping this one. Is the ext/xmlrpc extension also on >>> the list to be unbundled maybe for PHP-7.4? >> >> AFAIK, it isn't. Sorry for not having pursued this. > > Then I can create an RFC to unbundle it from the core and move it > together with the libxmlrpc library fork into PECL. Having > unmaintained extensions in the core and marked as experimental for the > last 18 years is not good I think. Is there enough time to do all this > until July 22nd (7.4 feature freeze)?
I think it's too late to start an RFC targeting PHP 7.4, since there is a minimum of two weeks for discussion and two weeks for voting. -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
