Re: deprecating xml-rpc and package.xml 1.0

Lukas Kahwe Smith a écrit :

Gregory Beaver wrote:

Arnaud Limbourg wrote:

Lukas Kahwe Smith wrote:

Arnaud Limbourg wrote:

Martin Jansen wrote:

     
On Wed Oct 18, 2006 at 08:5223PM -0500, Gregory Beaver wrote:
       
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.            

Did you read my mind? I was about to propose the same, but with 6 months time to handle instead of a year. The latter is fine for me though.

       
In particular, we need
to talk to Zend and figure out their who's who app.            
I think Steph Fox is our contact with regard to this.  If needed, I can

talk to her.

       
Comments?
          
This is an important change.  Let's go for it.
        

Sounds reasonnable.

In this context should someone devise a package v1 to v2 migration plan?

I actually meant to say "push" instead of "plan".

It is a good idea. I believe PFM would come into play ?

Simpler. run "pear convert" in your package directory, and then rm package.xml and mv package2.xml package.xml

what is the equivalent step if you are using PFM? Have a look on "basicConvert" example [1] i've recently updated to show how HTML_AJAX package xml 1.0 could be convert into package xml 2.0 Something almost equivalent to "pear convert" command. Take care, before to use, i think there is still a bug somewhere, because last changelog entry date is replaced by current date.

regards, Lukas

Hope it will help Lukas regards Laurent [1] http://cvs.php.net/viewvc.cgi/pear/PEAR_PackageFileManager/examples/basicConvert.php?revision=1.2&view=markup