2005/12/21, Jochen Wiedmann <[EMAIL PROTECTED]>: > On 12/21/05, Henri Gomez <[EMAIL PROTECTED]> wrote: > > > - Did we keep the current code (2.0.2 compatible) and have the > > 'deprecated' warning on 3.0 or did we update code to 3.0 requested > > methods, for example using PostMethod params instead of setHttp11. > > The former. I'd vote -1 for larger changes in the current project > stage. We can check such modifications in as soon as 2.0.1 is out. > However, being a maintenance release, it is really questionable > whether loosing downwards compatibility isn't even reserved for the > trunk?
Ok you're right and 3.0 is backward compatible with 2.0.2 (even with the deprecated). And as such we should reduce users problems when they forget to switch to http-client 2.0.2 to 3.0 when updgrading XMLRPC 2.0 to 2.0.1 Let keep hc 3.0 for next release. BTW, what SVN / branch should I use to get the latest XML-RPC head (3.0 ?)
