Breaking schema changes

[Mark Canonical Ramm-Christensen]

If there are *ANY* schema or internal or client API breaking changes we
need to start a new containers branch to land that stuff in, because we
don't yet have major version upgrades.

And we don't want to burn too many major version numbers while we are
building out the container stuff.

Once we have a containers branch, it should contain all of trunk (eg, merge
trunk and handle any merge conflicts before pushing to the containers
branch).

Also anything that gets merged into the containers branch should be moved
to that lane in the kanban board.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130528/8f77e95f/attachment.html>