Fix some introspection warnings
g_application_add_main_option: fix type signature

The flags argument is a GOptionFlags so use that type instead of 'int'.
goption: Add G_OPTION_FLAG_NONE

This is helpful to better document code, as G_OPTION_FLAG_NONE is more
readable than 0.
GApplication:handle-local-options: document return value

The return value for this signal was documented in the prose, but not
properly in a Returns: stanza.  Fix that.
Updated Marathi Translations
Updated Serbian translation
Update URLs library.gnome.org -> developer.gnome.org
gresource: Use GError in more places

The API gives us an error message, lets use it.
gresource: Make extract work better

When no section is specified, look for the resource to extract
in all sections - previously, we would stop after the first
section.
GVariant: say that serialized form needs an out-of-band length

This confused me for a while, because it isn't the same as D-Bus.
Like GVariant, the D-Bus serialization needs an out-of-band
endianness and type indicator, but unlike GVariant, serialized
D-Bus objects encapsulate their own length (often by starting with
a byte-count). This does come at some redundancy cost, so I can see
why the more efficient GVariant format does this the way it does;
but it's a difference between D-Bus and GVariant that seems worth
calling out.

It's also relevant for the designers of file or message-framing
formats: with D-Bus serialization it would be feasible to say "the file
starts with a little-endian D-Bus variant, followed by...",
but in GVariant you wouldn't be able to deserialize the variant
unless you either assume that it extends to end-of-file, or have
an explicit length.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=736975
Reviewed-by: Ryan Lortie
gsource: clarify restrictions on non-existant IDs

Document that one must not use the "by id" source APIs with non-existent
IDs.  The real justification behind this restriction is that the reuse
of source ids makes it unsafe to call these functions unless you're
absolutely sure that the source exists and it belongs to you.  If you
call one of these functions on a source that may already have been
removed then you run the risk of finding someone else's source (with
your reused id).

This also bails us out of a slightly tricky situation with respect to
the threadsafety of g_main_context_find_source_by_id().  The fact that
this function doesn't return a reference implies that its return value
cannot be safely accessed unless we already know for sure that a
reference is being held elsewhere (by example, by the main context
itself if we know that the source has not been removed).  The function
itself, however, performs an access to the value, which could result in
a crash.

If we mandate that it is only valid to call this function on
known-to-exist source IDs then we dodge this problem.

https://bugzilla.gnome.org/show_bug.cgi?id=736683
gmain: improve g_source_set_name thread safety

Step up thread safety on g_source_set_name() to the same standard as all
other GSource functions: after we are attached to a main context, this
function should be threadsafe.

https://bugzilla.gnome.org/show_bug.cgi?id=736683
Updated Danish translation
update zh_CN translation
update zh_CN translation
Revert "update zh_CN translation"

Add wrong po file
This reverts commit ee3d55573ff3731b2f92deb5e35decc316d53475.
Updated Hindi translation
update Punjabi Translation for 3.14 release
GLib 2.42.0
gtask: Fix a signed/unsigned integer comparison

The GSource times assigned to creation_time are always signed.

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