Hi! > xmlrpc is used quite a lot still (limesurvey f.e. or moodle as this > other reply confirmed), removing without previous warnings or not even > trying to get a maintainer before moving it sounds a bit like a bad > move to me.
Well, we're not destroying the code. Anybody who builds their own can as easily check out PECL repo, and distributions can and do build PECL modules without any problem. The difference is mainly whose responsibility it is. If it's in core, PHP team as a whole bears responsibility on what happens there, and if we don't actually have anybody to maintain it, the claim that we do is a lie, and we're making promises on which we can't deliver. So we should either seek maintainers or admit we don't maintain it. So I don't see it as a BC issue but mainly as an issue of clearly communicating of who is responsible for given extension and what promises we are making. That said, we probably need a bit better procedure on how that process should work, I'll try to write an RFC in my copious free time to set up guidelines and maybe do some re-inventarization of our extensions for 7.1. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
