Land "avoid XMLRPC" for bzr-2.3.?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We currently have 1 bug with a task for 2.3 which has not been landed:
  https://bugs.launchpad.net/bzr/2.3

It is mine: https://bugs.launchpad.net/bzr/2.3/+bug/397739
  LaunchpadDirectory shouldn't use xmlrpc

We decided to wait on that, because of interoperability with an existing
service. Which was wise, because there was specific fallout. (You can
push to +branch/* but it doesn't set up stacking correctly. So you have
to use ~user/project/branch to set up new branches, and then you can
access them as +branch/* to update them.)

> Martin Pool wrote on 2011-03-24: 	#29
> 
> This is is a nice speedup, but not a low-risk bugfix that we could
> put into an SRU. Given Natty is now in alpha freeze (iirc) and might
> get this uploaded before beta, I think it's arguably safe enough
> for 2.3 if we're sure it's safe in trunk, and if the lp stacking
> issues are addressed first. Otherwise, wontfix for 2.3.


I think we've ironed out the issues, but just wanted a poke on it,
whether I should try to finish off the backport or not.

I'm happy enough to just punt and make it WontFix on 2.3, but it really
depends on whether people want me to do the work or not.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3JIngACgkQJdeBCYSNAAN3zQCg1RkcSJhkHEGvXTnK/2V7EmhW
OvoAn15t+/uG4b9xIwabm1XDdh/MTxbL
=gIjV
-----END PGP SIGNATURE-----