build: Do not ship generated source-files in tarball
build: Make sure built-sources are introspected as needed
display: Don't focus the no-focus-window when sending WM_TAKE_FOCUS to a globally active window

Clients like on-screen keyboards try not to take focus when the user clicks
on their window by setting the Input hint to false. However, due to GTK+ and
GDK bugs, the public API for setting the Input hint to false don't remove
WM_TAKE_FOCUS from WM_PROTOCOLS, unintentionally putting them into Globally
Active mode.

These clients also expect that since they don't want to take focus, they want
the focus to remain on the existing window. In this case, for clients like
on-screen keyboards, it's so they can send synthesized keyboard events to the
focused window.

https://bugzilla.gnome.org/show_bug.cgi?id=710296
Add keyboard shortcut for Always on Top, bug 704831
doc: Fix file globs

Any files matching the previously used globs are no longer distributed,
breaking distcheck. Match the actual sources in compositor/, core/, meta/
and ui/ instead.
xrandr: use "hotplug_mode_update" property

Use the "hotplug_mode_update" connector property indicating that the
screen settings should be updated: get a new preferred mode on hotplug
events to handle dynamic guest resizing (where you resize the host
window and the guest resizes with it).

https://bugzilla.gnome.org/show_bug.cgi?id=711216
compositor: Initialize the plugin manager after initializing the output window

Plugins like gnome-shell may want to grab the output window immediately
before bouncing back to the mainloop.
compositor: Clean up comment

So it seems that we were intentionally delaying the output window,
although I wonder why...
screen: Laters are not GSources

This warns with the new GLib when we destroy the screen.

https://bugzilla.gnome.org/show_bug.cgi?id=711731
window: don't ignore resize button release event for move/resize actions

https://bugzilla.gnome.org/show_bug.cgi?id=710251