[ANNOUNCE] wayland 1.10.91

Fri May 6 11:17:23 UTC 2016

On Wed, 4 May 2016 11:46:23 -0700
Bryce Harrington <bryce at osg.samsung.com> wrote:

> On Wed, May 04, 2016 at 12:55:16AM -0700, Bryce Harrington wrote:
> > Here's the alpha for the upcoming 1.11 release.  I'll summarize the
> > major features for this release in the beta announcement, but see below
> > for the detailed listing.
> > 
> > The schedule going forward is:
> > 
> >   √ 1.11-alpha on May 3rd.  Major features done by this point.
> > 
> >   - 1.11-beta around May 17th.
> > 
> >   - 1.11-rc1 around May 24th.
> > 
> >   - 1.11.0 release around May 31st.
> > 
> > At this time consider Wayland in feature freeze mode.  We'll continue to
> > land minor enhancements through beta, and focus on bug fixes thereafter.  
> 
> Do we need to up the version requirements for weston's libwayland client
> or server dependency, or the version of wayland-protocol?

Hi Bryce,

Wayland-protocol deps should all be dealt with as they happen. I
believe we have the policy to land changes in wayland-protocols first
and have a w-p release, and then land weston patches depending on them,
bumping the dependency on configure.ac at the same time. That's what
I've been doing anyway.

Unfortunately, we cannot do the same with libwayland since it would add
considerable delay in landing such weston patches.

> In both cases, it looked to me that no, Weston doesn't depend on any of
> the recent changes.  We currently depend on wayland-protocols 1.2, and
> the changes for 1.3 are primarily tablet protocol, support of which
> doesn't sound like landable for Weston at this point.  Post 1.3 w-p
> changes of note are the presentation-time protocol, which I'm not
> certain of.

None of the presentation-time changes after 1.2 and 1.3 change any
semantics, so no bump needed for them.

> Weston currently depends on wayland-server 1.10 and wayland-client
> 1.5.91.  I could just bump the server version just to be safe, but
> offhand I'm not recalling if we did introduce any changes this cycle
> that actually requires it?  As to the client dependency, I've never been
> clear on when that should be bumped, or if what the implications on
> clients would be if we did; I'd love some advice/clarification on that
> for future reference if nothing else.

I looked through libwayland changes post-1.10 release, and the only ABI
change is the addition of the proxy wrappers, which is not used in
Weston. ABI additions are easy to spot by looking for changes to the
headers. It's unlikely to have other kind of changes, except perhaps
scanner.c generated code.

To keep things simpler, I would suggest we keep the all of
libweston-server, -client, and -cursor dependencies at the same number
in Weston. I'm not sure you even can build things from Weston without
both -server and -client. If you use both, they surely are the same
version.

The client dependency may have been forgotten, and the server
dependency will hide any issues it might have.

Of course, whenever anyone sends a Weston patch that needs something
new from libwayland, the commit message should say so. Maybe we could
add a XXX comment in configure.ac also, like my weston patches do for
wayland-protocols before there is a wayland-protocols release?

> Other than that, I've been assuming that if there are any other
> build-dependency changes, they'd have been patched directly.  But it
> would be great at this point to do fresh builds/installs on whatever
> hardware variations are at hand just to doublecheck, and get patches in
> for fixes.  I'll make a priority to review those.

Indeed.

Thanks,
pq

> > Changes:
> > --------
> > 
> >     Auke Booij (1):
> >       protocol: add support for cross-interface enum attributes
> > 
> >     Bill Spitzak (1):
> >       doc: Use enum argument type to make links in protocol documentation
> > 
> >     Bryce Harrington (3):
> >       configure.ac: bump to version 1.10.90 for open development
> >       doc: Note strong recommendation to use S-o-b in contributions
> >       configure.ac: bump to version 1.10.91 for the alpha release
> > 
> >     Derek Foreman (9):
> >       resource-test: Use wl_seat instead of wl_display for testing
> >       server: validate resource versions at creation time
> >       build: Add an --enable-fatal-warnings configure option
> >       build: build distcheck with --enable-fatal-warnings
> >       Revert "build: build distcheck with --enable-fatal-warnings"
> >       Revert "server: validate resource versions at creation time"
> >       shm: Split pool reference counting into external and internal references
> >       shm: Defer wl_shm_pool_resize if a pool has external references
> >       shm: Log a warning if a shm buffer address is requested when it may be invalid
> > 
> >     Emil Velikov (3):
> >       scanner: move include directives before extern "C" wrapper
> >       server: move include directives before extern "C" wrapper
> >       utils: move include directives before extern "C" wrapper
> > 
> >     Eric Engestrom (7):
> >       protocol: fix spelling mistake
> >       wayland-client: fix spelling mistake
> >       client: fix typo
> >       server: fix typo
> >       util: fix typo
> >       doc: fix typos
> >       tests: fix typo
> > 
> >     Jonas Ådahl (5):
> >       client: Don't segfault when receiving error on destroyed object
> >       client: Make proxy_destroy a static function
> >       client: Introduce proxy wrappers
> >       tests/queue-test: Add tests for proxy wrappers
> >       client: Fix wl_display_roundtrip_queue() race condition
> > 
> >     Marek Chalupa (2):
> >       tests: add test for receiving an error on destroyed object
> >       connection: remove redundant assignment
> > 
> >     Pekka Paalanen (2):
> >       build: fix ./configure --disable-dtd-validation
> >       scanner: avoid executable stack
> > 
> >     Peter Hutterer (2):
> >       doc: generate doxygen html output from the scanner
> >       doc: link between client and server doc and to the wayland book
> > 
> >     Sergi Granell (1):
> >       server: Fix shm_create_pool size fail path fd leak
> > 
> >     Yong Bakos (7):
> >       doc: Ignore html subdirectory.
> >       ignore: Add *.dtd.embed
> >       scanner: Fix spacing of @param
> >       protocol: Correct grammar and spelling
> >       doc: Hyphenate compound adjectives window-local, surface-local
> >       protocol: Hyphenate compound adjective surface-local
> >       protocol: Add summaries to event parameters
> > 
> > git tag: 1.10.91
> > http://wayland.freedesktop.org/releases/wayland-1.10.91.tar.xz
> > MD5:  5a34f0b2dde3512bfd0c9b2a2af9034d  wayland-1.10.91.tar.xz
> > SHA1: 32568737ab49a5ee3bafcd5b7d002094875e0feb  wayland-1.10.91.tar.xz
> > SHA256: cb40de85488eb138e0f25b86b161c880c8115e07b7a89ec24c8cc99d02b4ca31  wayland-1.10.91.tar.xz
> > PGP:  http://wayland.freedesktop.org/releases/wayland-1.10.91.tar.xz.sig
> > 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20160506/6b6bf7f0/attachment.sig>