Wayland and Weston 0.95.0 released
Pekka Paalanen
ppaalanen at gmail.com
Tue Jul 24 13:48:51 PDT 2012
On Tue, 24 Jul 2012 16:32:18 -0400
Kristian Høgsberg <hoegsberg at gmail.com> wrote:
> With the 0.95 release we start maintaining protocol and client API
> stability. Going forward, we will try to not break any clients or
> toolkits that are written agains the 0.95 protocol and client API. We
> don't completely freeze yet, we'll do that with the 1.0 release, but
> from now on we'll use the versioning mechanism when possible and only
> break API if absolutely necessary. This also doesn't mean that the
> protocol won't be extended in the future, just that we will not change
> what's there now.
>
> To clarify, we're freezing the protocol, as described by
> protocol/wayland.xml in the Wayland repository and the client API/ABI
> defined by wayland-client.h and the headers generated from
> wayland.xml. In particular, we're not freezing the protocol
> interfaces defined by Weston and we're not freezing the wayland-server
> API. Also, for the protocol interfaces (wl_drm) and libraries (gbm)
> that are part of mesa, we'll release those with the upcoming mesa 8.1,
> at which point we'll treat those as stable too.
>
> I'll follow up with a description of how the interface versioning and
> deprecation is supposed to work.
Hi,
does this freeze include wl_shell and wl_shell_surface interfaces,
which reside in wayland.xml?
I thought those were considered non-core and in flux.
Thanks,
pq
More information about the wayland-devel
mailing list