Re: deprecating xml-rpc and package.xml 1.0

Gregory Beaver wrote: > Hi, > > As you can see from the stats page I've put up at > http://pear.php.net/~greg/stats/ > we no longer have any significant usage of PEAR 1.3 to download > packages. This is a good sign of the adoption rate of PEAR 1.4.x, and I > think it is time to deprecate package.xml 1.0 and specifically the > xml-rpc server. Deprecation does *not* mean disabling. It means > putting out a big warning that 1 year from now we will turn off the > server, and notify as many sources as possible. In particular, we need > to talk to Zend and figure out their who's who app. Disabling any > sooner than 1 year after the announcement would be fallacy in my opinion. Hi Greg, I've just lately downloaded PEAR 1.3.3 (?) myself I must admit, and as such am included in the xml-rpc-usagestats. That was instatlling a CentOS-basesystem with a shipped package php-pear. And instead of upgrading directly to PEAR 1.4.x you even needed to upgrade to at least PEAR 1.3.3 (I think it said). (Okay, I could/should have used go-pear to install pear there - but anyway.) So I suspect that some portion of the requests you see are not necessarily people actively "using" xml-rpc for daily business, but maybe upgrading a from a PEAR-installation shipped with a distribution. That said, in the term of 1 year I suspect even this side-effect to go down since also the conservative distributions like RHEL/CentOS and such should have a new release by then, which hopefully includes PEAR 1.4.x by default. That having said, I agree that an announcement with a 1 year-period sounds reasonable. Stopping to accept packages without package.xml 2.0 after 1/1/07 (or maybe even earlier?) sounds fine for me as well, since conversion is quite easy to do - and I think you can expect that move from active pear-devs firing out a new release. Regards, Stefan