Considering moving all Launchpad branches to 2a - based formats

[Aaron Bentley]

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

On 11-09-18 06:04 PM, Michael Hudson-Doyle wrote:
> The xml-rpc service is run on the same appservers as the rest of 
> Launchpad.  XML-RPC and httpd logs don't get on in a very
> informative way, but resolve_lp_path is the single method of the 
> xmlrpc.launchpad.net/bazaar endpoint, so we know that lines like
> this:
> 
> 91.189.89.30 - "XXX.XXX.XXX.XXX" "xmlrpc.launchpad.net"
> [18/Sep/2011:05:11:41 +0000] "POST /bazaar/ HTTP/1.1" 200 649 6
> 0.0294139385223 84 101 "Anonymous"
> "BazaarApplication:PublicCodehostingAPI" "" "bzr/2.3.4 (urllib)"
> 
> is bzr resolving a lp: URL.

Thanks!

So according to the logs, here's the breakdown for one of our machines
for yesterday:
$ zgrep xmlrpc.launchpad.net launchpad-access47.log-20110918|cut -f 19
- -d ' '|sort|uniq -c
    100 "bzr/2.1.4
      1 "bzr/2.2.2
    103 "bzr/2.2.4
      2 "bzr/2.2b4
     11 "bzr/2.3.1
      6 "bzr/2.3.3
    475 "bzr/2.3.4
      9 "bzr/2.3b2
      3 "bzr/2.4.0
     15 "bzr/2.4.1
     23 "bzr/2.4b5
      1 "bzr/2.5.0dev1

As far as I know, this is representative of all our machines.  I've
looked at the logs for September, and I haven't found any use of bzr
2.0, much less an earlier version.

I've heard back from five (of 20) project owners whose projects have
old-format trunks, and none of them are concerned about moving to 2a.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk53SnsACgkQ0F+nu1YWqI0eLACeJgvT0JK6v6cbbnM+Yx3j6hB0
Br0An1uuCh0NQI1auWlgBus7FOizgDfb
=+B8t
-----END PGP SIGNATURE-----