QA for Bazaar Upgrades

When we upgrade Bazaar, there are a number of moving parts to test.

While exhaustive testing is almost impossible, we can make sure all the basics work.

• Push a new branch up, and make sure it is scanned correctly
• Should test at least one code import, and ideally one of each type
  • Suggestions:

    • http://codespeak.net/svn/user/mwh/pydoctor/trunk - https://code.staging.launchpad.net/pydoctor

    • git://gitorious.org/be/be - https://code.staging.launchpad.net/bugs-everywhere

    • https://etherpad.googlecode.com/hg/ - https://code.staging.launchpad.net/etherpad

    • :pserver:anonymous@ufraw.cvs.sourceforge.net:/cvsroot/ufraw ufraw - https://code.staging.launchpad.net/~vcs-imports/ufraw/trunk (actually, this takes a long time. Maybe use something else?)

• Loggerhead should be tested to check branch access
• Push up a modifed branch, propose a merge and make sure the diff is generated
• Push/pull some large branches (perhaps lp:gcc?)

Probably much more but this is a start.

It is usually also a good idea to look at the relevant bzr release notes to see if there is anything else that has changed that is worth testing.