On Mon, Jul 18, 2016 at 3:41 PM, Niklas Keller <m...@kelunik.com> wrote: > 2016-07-18 9:54 GMT+02:00 Pierre Joye <pierre....@gmail.com>: >> >> hi, >> >> On Mon, Jul 18, 2016 at 7:12 AM, Davey Shafik <da...@php.net> wrote: >> > The only negative I see for this is that it reinforces PECL as being >> > Siberia. Having said that, it's better than deleting them, and they >> > shouldn't be in core. >> >> I see other, one of them is BC breaks. > > > Moving extensions to PECL is allowed in x.y.z to x.y+1.z: Extensions support > can be ended (moved to pecl) > > See: https://wiki.php.net/rfc/releaseprocess
I wrote it, so yes, I do know that. However allowed does not mean "let do it for any ext at any point release". xmlrpc is still widely used and it does not seem to require a lot of work. It has been stable for a long time and new bugs may be mostly due to 7 migration as we have seen in many other extensions. Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
