Mir in Ubuntu

Daniel van Vugt daniel.van.vugt at canonical.com
Wed Jun 5 03:34:22 UTC 2013

The protocol stability is not a top priority yet. Because it's totally 
hidden behind the API. Protocol changes can still occur with careful 
package versioning. Because we can continue to release updates to the 
shared mir client library, with opaque changes to the protocol.

It's the API/ABI we need to stabilize sooner because we can't control 
the release of third-party apps/toolkits/shells once they start appearing.

The protocol details don't matter until/unless you have multiple 
implementations the protocol. And for Mir, that's a long way off.

On 28/05/13 17:30, Alan Griffiths wrote:
> On 27/05/13 07:19, Christopher James Halse Rogers wrote:
>> Since the system compositor depends on the Mir server API, which we've
>> made no effort to make ABI-stable, I don't think we can reasonably
>> autoland mir+unity-system-compositor into the distro.
> We've always said "you don't need it (yet)" but the time has come to
> have a plan for stabilizing the MIR ABI (and also the underlying protocol).

More information about the Mir-devel mailing list