[#390502] upgrading bzr trunk to 2a

[Vincent Ladeuil]

>>>>> "martin" == Martin Pool <mbp at canonical.com> writes:

    martin> I think now would be a great time to switch the bzr
    martin> trunk to 2a format.  After some discussion what I
    martin> propose to do is:

    martin> 0- Test upgrading bzr.dev on my own machine

As a parallel approach, I upgraded the shared repositories used
by the slaves in the test farm.

Each slave runs the test suite by doing:

  bzr [checkout|update] http://bazaar.launchpad.net/~bzr/bzr/trunk <somewhere>

and do so with its locally installed bzr.

In my case it included 1.17 (hardy), 1.18(karmic) and
2.1dev(jaunty, tiger, leopard).

The summary is that 2.1dev is the one to use.  Some more info is
available at the test farm (search for builds with failures in
the 'update' steps).

The progress report is better for 1.17/1.18 but reveals a amount
of data transferred that seems excessive.

2.1dev progress report seems to be too deep and the interesting
part is not shown. The data transfer-ed looks better though.

<snip/>

    martin> I don't think this requires intervention from anyone except some help
    martin> from spm to do the upgrade and I'll send mail about any changes needed
    martin> to your pqm-submit setup.  If you see any problems with it, yell now.

Sounds fine.

       Vincent