Breaking schema changes

[Tim Penhey]

On 29/05/13 02:58, Mark Canonical Ramm-Christensen wrote:
> 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.

I *think* that we can get the container stuff in without breaking
changes.  Especially after my chat with William this morning.

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

I *think* we may also be able to get the constraint matching stuff in
without a break (hopefully - although this one requires a little more
thought).

> 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). 

Lets hope we don't need this.

Tim