import branches should always be in Bazaar's default format

We should also send an email to the launchpad-users list telling them that we are going to do this work.

Secondarily, we should file an RT to run a script to upgrade all of the branches that aren't automatically upgraded.

Does this mean that projects that want to use a higher format (one supported by Launchpad, just not the current Bzr default) would not be able to?

Yes. "you" don't get much control over the import process, basically.

On Wed, Feb 11, 2009 at 7:42 AM, Karl Fogel <email address hidden> wrote:
> Does this mean that projects that want to use a higher format (one
> supported by Launchpad, just not the current Bzr default) would not be
> able to?

Not really. The bug is restricted to branches imported from CVS or
Subversion -- branches that only we can write to.

Landed in rev 7901

This bug fix seems to no longer apply.

https://code.edge.launchpad.net/~vcs-imports/vala/trunk is importing, but is *not* in Bazaar's default format.

Yeah, because upgrading to 2a format can take days, and trying to do it for every branch would flatten the importds. We should probably try to come up with some way of doing a rolling upgrade, or at the very least upgrade on request.

On Sun, Oct 10, 2010 at 9:23 PM, Michael Hudson-Doyle
<email address hidden> wrote:
> Yeah, because upgrading to 2a format can take days, and trying to do it
> for every branch would flatten the importds.  We should probably try to
> come up with some way of doing a rolling upgrade, or at the very least
> upgrade on request.
>

Upgrade on request would be good. A user wanted to do this, which is
what led me to this bug.