Breaking schema changes

[Mark Canonical Ramm-Christensen]

Mostly, it is to combat the perception that we are making breaking changes
at a rapid pace, and therefore aren't stable enough for real world use.

Secondarily, it is so that we are aware of and controlling when
backwards incompatible changes land in trunk, and are preserving the
ability to release 2.0 as an important milestone (it's only psychological,
but that does not mean it's not *important*).

--Mark

On Tue, May 28, 2013 at 7:37 PM, David Cheney <david.cheney at canonical.com>wrote:

>
> And we don't want to burn too many major version numbers while we are
>> building out the container stuff.
>>
>>
> Can you please explain the reasoning behind this statement. Is it
>
> a. psychological, some people need to have an consecutive sequence of
> releases ?
> b. operational, our Ubuntu release policy requires that certain semantic
> versioning rules apply
> c. something else ?
>
> Cheers
>
> Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130528/65e7c1df/attachment.html>