Wayland and Weston 0.95.0 released

[Kristian Høgsberg]

On Wed, Jul 25, 2012 at 3:35 AM, Tiago Vignatti
<tiago.vignatti at linux.intel.com> wrote:
> On 07/24/2012 11:48 PM, Pekka Paalanen wrote:
>>
>> 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.
>
>
> I had the same feeling here. And we should change wl_shell to
> wl_desktop_shell for once.

No, it's all frozen now.  We can add to it, but we're done protocol
breaks and whimsical renames.  We'll probably want to revise it later
on, and it may in fact be nice to reserver wl_desktop_shell for the
new interface.  But we're not introducing a new interface now, we're
just going to pile on wl_shell (in a backwards compatible way) until
it breaks.  There's a lot of functionality in wl_shell that toolkits
depend on for basic functionality and we can't just keep changing that
every week.

Kristian