upgrade bzr.dev to rich roots?

[John Arbash Meinel]

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

Robert Collins wrote:
> So, I'd like to be dogfooding --development6-rich-root. The project I
> write most code for is bzr, but we're not a rich-root using project.
> 
> So, I propose we upgrade bzr to rich roots.
> 
> This requires:
> - a final decision about what root id entries to create [John proposed
>    reevaluating the current converter a week or so back].
> - testing and making sure we can successfully upgrade stacked branches
>    to rich-root. [e.g. by unstacking then upgrading, or whatever]
> - some coordination about when we are doing the upgrade, so that people
>    can upgrade their stacked branches beforehand.
> - do the upgrade [backup the trunk repo so people that upgrade stacked
> branches late can still do so, and run bzr upgrade --1.9-rich-root.
> 
> -Rob
>  

For me personally, this would tend to have a lot of knock-on effects, as
I have 1 shared branch between bzr + bzr plugins. I can switch that
reasonably easily.

I would venture the bigger problem is the upgrade time for everyone
working on the project. I suppose if we provide an official location for
download, and then document moving your existing repo out of the way,
copying from remote, and then you only need to upgrade the last few bits.

I thought stacking a non-rich-root on a rich-root was ok. Just that
stacking an XML repo on top of a brisbane-core one would be tricky.

I don't know what the upgrader, etc actually handles, but considering
that a stacked branch on top of a rich root should be ~ the same as just
doing a "bzr branch" from a non-rich-root source to a rich-root one,
which works just fine right now.

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

iEYEARECAAYFAkncrVgACgkQJdeBCYSNAANdnwCg0HQ5vPP4YWjC6WUxDiAOtefN
eXQAoJHOZ7I2MicFMbpb0fbAEM+umN3P
=ISLG
-----END PGP SIGNATURE-----