=== release 1.4.5 ===

2014-12-18  Sebastian Dröge <slomo@coaxion.net>

	* configure.ac:
	  releasing 1.4.5

2014-12-16 12:21:59 +0100  Wim Taymans <wtaymans@redhat.com>

	* gst/gstbufferpool.c:
	  bufferpool: log reason for discarded buffers
	  PERFORMANCE log the reason why a buffer could not be recycled in the
	  bufferpool.

2014-10-07 16:44:45 +0200  Edward Hervey <bilboed@bilboed.com>

	* libs/gst/base/gstbasesink.c:
	  basesink: clamp reported position based on direction
	  When using a negative rate (rate being segment.rate * segment.applied_rate),
	  we will end up reporting decreasing positions, therefore adjust the clamping
	  against last reported value accordingly.
	  Fixes positions getting properly reported with applied_rate < 0.0
	  https://bugzilla.gnome.org/show_bug.cgi?id=738092

2014-11-28 14:15:30 -0300  Thiago Santos <thiago.sousa.santos@collabora.com>

	* libs/gst/base/gstbaseparse.c:
	  baseparse: update the duration variable before emitting the bus
	  Otherwise the application might still get the old value if it asks
	  between the message and the real update.

2014-11-28 16:25:02 +0100  Edward Hervey <bilboed@bilboed.com>

	* gst/gstelement.c:
	  element: Fix doc and default implementation of send_event
	  The documentation states that gst_element_send_event is to "send an event
	  to an element".
	  Therefore we *send* upstream events to a source pad and downstream events
	  to a sink pad

2014-11-28 11:16:00 +0100  Edward Hervey <bilboed@bilboed.com>

	* gst/gstelement.c:
	  element: Figure default send_event direction handling
	  If we get a downstream event we want to send it to a random SINK pad
	  (and vice-versa).

2014-11-23 05:45:24 -0300  Thiago Santos <thiagoss@osg.samsung.com>

	* plugins/elements/gstqueue2.c:
	  queue2: percentage is relative to high-percent
	  When comparing percentage values, compare with 0-100 scale as it
	  has already been made relative to 0-high_percent, otherwise we mark
	  the queue as not buffering and report a 50% to the user. This leads to
	  a buffering stall as the user assumes the queue is still buffering but
	  it thinks it isn't.
	  https://bugzilla.gnome.org/show_bug.cgi?id=736969

2014-11-23 05:42:51 -0300  Thiago Santos <thiagoss@osg.samsung.com>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: percentage is an absolute value
	  multiqueue's queues stored percent value is the percentage from 0
	  to 100 (max-size-*) and should be compared with the requested limit
	  (high_percentage) set by the user and not with 100% to check if
	  buffering should stop. Otherwise we are only stopping buffering when the
	  queue gets completely full.

2014-11-20 13:34:32 +0100  Wim Taymans <wtaymans@redhat.com>

	* gst/gststructure.c:
	* tests/check/gst/gststructure.c:
	  structure: don't overread input when searching for "
	  When searching for the string terminator don't read past the ending
	  0-byte when escaping characters.
	  Add unit test for various escaping cases.

2014-11-03 17:46:57 +0000  Vincent Penquerc'h <vincent.penquerch@collabora.co.uk>

	* gst/gstpad.c:
	  pad: fail dropped queries
	  Previously, dropping a query from a pad probe would deem the
	  query succeeded, and the caller might then assume the query's
	  results are valid, and thus dereference an invalid object
	  such as a GstCaps.
	  We now assume dropped queries did not succeed. Dropped events
	  and buffers are still deemed a success.

2014-11-12 11:30:51 +0100  Haakon Sporsheim <haakon.sporsheim@gmail.com>

	* gst/gsttask.c:
	* tests/check/gst/gsttask.c:
	  task: Fix pause/stop race condition
	  If a task thread is calling pause on it self and the
	  controlling/"main" thread stops the task, it could end in a race
	  where gst_task_func loops and then checks for paused after the
	  controlling thread just changed the task state to stopped.
	  Hence the task would actually call func again even though it was
	  both paused and stopped.
	  https://bugzilla.gnome.org/show_bug.cgi?id=740001

=== release 1.4.4 ===

2014-11-06 12:51:42 +0100  Sebastian Dröge <sebastian@centricular.com>

	* ChangeLog:
	* NEWS:
	* RELEASE:
	* configure.ac:
	* docs/plugins/inspect/plugin-coreelements.xml:
	* gstreamer.doap:
	* win32/common/config.h:
	* win32/common/gstversion.h:
	  Release 1.4.4

2014-11-06 12:25:58 +0100  Sebastian Dröge <sebastian@centricular.com>

	* po/af.po:
	* po/az.po:
	* po/be.po:
	* po/bg.po:
	* po/ca.po:
	* po/cs.po:
	* po/da.po:
	* po/de.po:
	* po/el.po:
	* po/en_GB.po:
	* po/eo.po:
	* po/es.po:
	* po/eu.po:
	* po/fi.po:
	* po/fr.po:
	* po/gl.po:
	* po/hr.po:
	* po/hu.po:
	* po/id.po:
	* po/it.po:
	* po/ja.po:
	* po/lt.po:
	* po/nb.po:
	* po/nl.po:
	* po/pl.po:
	* po/pt_BR.po:
	* po/ro.po:
	* po/ru.po:
	* po/rw.po:
	* po/sk.po:
	* po/sl.po:
	* po/sq.po:
	* po/sr.po:
	* po/sv.po:
	* po/tr.po:
	* po/uk.po:
	* po/vi.po:
	* po/zh_CN.po:
	* po/zh_TW.po:
	  Update .po files

2014-10-24 12:51:07 +0100  Tim-Philipp Müller <tim@centricular.com>

	* libs/gst/base/gstbasesink.c:
	  basesink: don't unlock mutex that is not locked
	  Fixes 'Attempt to unlock mutex that was not locked'
	  warning with newer GLibs when sink is shut down in
	  certain situations. Triggered by the decodebin
	  test_reuse_without_decoders unit test in -base
	  sometimes, esp. on slower machines.

2014-10-16 10:13:14 +0400  Andrei Sarakeev <sarakusha@gmail.com>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: Wake up any waiting streams if the current one goes EOS
	  Otherwise we might have unlinked streams waiting.
	  https://bugzilla.gnome.org/show_bug.cgi?id=738198

2014-10-08 15:37:37 +0200  Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>

	* docs/pwg/advanced-negotiation.xml:
	  docs: pwg: fix typo in 'Dynamic negotiation' section
	  The point of this example is to show how to set caps
	  on the source pad once it has been set on the sink pad.
	  So, in passthrough mode, the caps is just copied to the
	  source pad.
	  https://bugzilla.gnome.org/show_bug.cgi?id=738153

2014-10-06 13:38:21 +0200  Nicolas Huet <nicolas.huet@parrot.com>

	* gst/gstsystemclock.c:
	  systemclock: fix multi-thread entry status issue
	  Running two threads, one executing the timer and one unscheduling it, the
	  unscheduled status set by the second thread is sometimes overwritten by the
	  first one.
	  https://bugzilla.gnome.org/show_bug.cgi?id=737999

2014-09-25 16:21:51 +0100  Tim-Philipp Müller <tim@centricular.com>

	* tests/check/libs/baseparse.c:
	  tests: fix caps leak in baseparse unit test

2014-10-03 13:14:25 +0200  Matej Knopp <matej.knopp@gmail.com>

	* tests/check/libs/baseparse.c:
	  tests: baseparse: set_sink_caps vfunc should't take ownership of the caps
	  https://bugzilla.gnome.org/show_bug.cgi?id=737762

2014-10-08 09:37:41 -0700  Aleix Conchillo Flaqué <aleix@oblong.com>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: don't lock multiqueue when pushing serialized queries
	  If we are pushing a serialized query into a queue and the queue is
	  filled, we will end in a deadlock. We need to release the lock before
	  pushing and acquire it again afterward.
	  https://bugzilla.gnome.org/show_bug.cgi?id=737794

2014-10-02 14:55:22 +0300  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstqueue.c:
	  queue: Add missing break in switch

2014-09-27 20:10:34 +0200  Matej Knopp <matej.knopp@gmail.com>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: update segment position on GAP events to calculate levels properly
	  https://bugzilla.gnome.org/show_bug.cgi?id=737498

2014-10-02 11:00:32 +0300  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstqueue.c:
	  queue: update segment position on GAP events to calculate levels properly
	  https://bugzilla.gnome.org/show_bug.cgi?id=737498

2014-10-02 10:57:43 +0300  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstqueue2.c:
	  queue2: update segment position on GAP events to calculate levels properly
	  https://bugzilla.gnome.org/show_bug.cgi?id=737498

2014-10-02 10:13:28 +0300  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstcapsfilter.c:
	  capsfilter: Push pending events before a buffer also if upstream never configured caps but we have srcpad caps already
	  Otherwise we never send pending events downstream that arrive after we
	  configured caps on the srcpad.
	  https://bugzilla.gnome.org/show_bug.cgi?id=737735

2014-09-24 10:11:54 +0200  Thibault Saunier <tsaunier@gnome.org>

	* scripts/gst-uninstalled:
	  scripts: Handle gst-python in gst-uninstalled
	  https://bugzilla.gnome.org/show_bug.cgi?id=709082

=== release 1.4.3 ===

2014-09-24 12:19:55 +0300  Sebastian Dröge <sebastian@centricular.com>

	* ChangeLog:
	* NEWS:
	* RELEASE:
	* configure.ac:
	* docs/plugins/inspect/plugin-coreelements.xml:
	* gstreamer.doap:
	* win32/common/config.h:
	* win32/common/gstversion.h:
	  Release 1.4.3

2014-09-24 11:15:07 +0300  Sebastian Dröge <sebastian@centricular.com>

	* po/af.po:
	* po/az.po:
	* po/be.po:
	* po/bg.po:
	* po/ca.po:
	* po/cs.po:
	* po/da.po:
	* po/de.po:
	* po/el.po:
	* po/en_GB.po:
	* po/eo.po:
	* po/es.po:
	* po/eu.po:
	* po/fi.po:
	* po/fr.po:
	* po/gl.po:
	* po/hr.po:
	* po/hu.po:
	* po/id.po:
	* po/it.po:
	* po/ja.po:
	* po/lt.po:
	* po/nb.po:
	* po/nl.po:
	* po/pl.po:
	* po/pt_BR.po:
	* po/ro.po:
	* po/ru.po:
	* po/rw.po:
	* po/sk.po:
	* po/sl.po:
	* po/sq.po:
	* po/sr.po:
	* po/sv.po:
	* po/tr.po:
	* po/uk.po:
	* po/vi.po:
	* po/zh_CN.po:
	* po/zh_TW.po:
	  Update .po files

2014-06-03 14:23:30 +0200  Thibault Saunier <tsaunier@gnome.org>

	* plugins/elements/gstcapsfilter.c:
	  capsfilter: Remove EOS event from pending_event list on FLUSH_STOP
	  https://bugzilla.gnome.org/show_bug.cgi?id=709868

2014-09-22 19:05:32 +0200  Marcin Kolny <marcin.kolny@flytronic.pl>

	* gst/gstdatetime.h:
	  datetime: added missing include directives
	  https://bugzilla.gnome.org/show_bug.cgi?id=737133

2014-09-23 14:31:29 +0200  Thibault Saunier <tsaunier@gnome.org>

	* plugins/elements/gstqueue.c:
	  queue: Do not forget to release the QUEUE_LOCK in the out_flow_error path
	  Avoiding deadlocks!

2014-09-22 09:33:04 +0200  Thibault Saunier <tsaunier@gnome.org>

	* plugins/elements/gstqueue.c:
	  queue: Do not hold GST_QUEUE_LOCK while posting ERROR messages
	  This might create deadlocks and we need to avoid holding element
	  specific lock while posting messages
	  For example a deadlock will happen if while posting the message,
	  someone connected on the bus (sync) tries to DOT the pipeline.
	  https://bugzilla.gnome.org/show_bug.cgi?id=737102

2014-08-13 14:02:47 +0200  Thibault Saunier <tsaunier@gnome.org>

	* scripts/git-update.sh:
	  script:udpate: Try to rebase local changes when updating

2014-09-19 12:02:46 -0300  Thiago Santos <thiagoss@osg.samsung.com>

	* plugins/elements/gstqueue2.c:
	* plugins/elements/gstqueue2.h:
	  queue2: do not post buffering messages holding the lock
	  It might cause deadlocks to post messages while holding the queue2
	  lock. To avoid this a new boolean flag is set whenever a new
	  buffering percent is found. The message is posted after the lock
	  is released.
	  To make sure the buffering messages are posted in the right order, messages
	  are posted holding another lock. This prevents 2 threads trying to post
	  messages at the same time.
	  https://bugzilla.gnome.org/show_bug.cgi?id=736969

=== release 1.4.2 ===

2014-09-19 14:19:08 +0300  Sebastian Dröge <sebastian@centricular.com>

	* ChangeLog:
	* NEWS:
	* RELEASE:
	* configure.ac:
	* docs/plugins/inspect/plugin-coreelements.xml:
	* gstreamer.doap:
	* win32/common/config.h:
	* win32/common/gstversion.h:
	  Release 1.4.2

2014-09-19 10:45:45 +0300  Sebastian Dröge <sebastian@centricular.com>

	* po/af.po:
	* po/az.po:
	* po/be.po:
	* po/bg.po:
	* po/ca.po:
	* po/cs.po:
	* po/da.po:
	* po/de.po:
	* po/el.po:
	* po/en_GB.po:
	* po/eo.po:
	* po/es.po:
	* po/eu.po:
	* po/fi.po:
	* po/fr.po:
	* po/gl.po:
	* po/hr.po:
	* po/hu.po:
	* po/id.po:
	* po/it.po:
	* po/ja.po:
	* po/lt.po:
	* po/nb.po:
	* po/nl.po:
	* po/pl.po:
	* po/pt_BR.po:
	* po/ro.po:
	* po/ru.po:
	* po/rw.po:
	* po/sk.po:
	* po/sl.po:
	* po/sq.po:
	* po/sr.po:
	* po/sv.po:
	* po/tr.po:
	* po/uk.po:
	* po/vi.po:
	* po/zh_CN.po:
	* po/zh_TW.po:
	  Update .po files

2014-09-19 00:33:58 +0100  Tim-Philipp Müller <tim@centricular.com>

	* docs/pwg/advanced-tagging.xml:
	* docs/pwg/intro-basics.xml:
	  docs: pwg: fix some links to the API docs
	  https://bugzilla.gnome.org/show_bug.cgi?id=736762

2014-09-17 17:17:10 +0200  Ognyan Tonchev <ognyan@axis.com>

	* plugins/elements/gsttypefindelement.c:
	  typefindelement: do not leak sticky events in flush_stop
	  https://bugzilla.gnome.org/show_bug.cgi?id=736813

2014-09-16 13:48:18 +0200  Ognyan Tonchev <ognyan@axis.com>

	* gst/gstevent.c:
	  event: add annotations to gst_event_parse_toc_select()
	  https://bugzilla.gnome.org/show_bug.cgi?id=736739

2014-09-16 12:17:48 +0200  Ognyan Tonchev <ognyan@axis.com>

	* gst/gstquery.c:
	  query: Add annotations to gst_query_add_allocation_pool()
	  https://bugzilla.gnome.org/show_bug.cgi?id=736736

2014-09-11 18:01:58 -0300  Thiago Santos <thiagoss@osg.samsung.com>

	* plugins/elements/gstmultiqueue.c:
	* plugins/elements/gstmultiqueue.h:
	  multiqueue: do not post messages holding the lock
	  It might cause deadlocks to post messages while holding the multiqueue
	  lock. To avoid this a new boolean flag is set whenever a new buffering percent
	  is found. The message is posted after the lock can be released.
	  To make sure the buffering messages are posted in the right order, messages
	  are posted holding another lock. This prevents 2 threads trying to post
	  messages at the same time.
	  https://bugzilla.gnome.org/show_bug.cgi?id=736295

2014-09-15 16:38:17 +0200  Aurélien Zanelli <aurelien.zanelli@parrot.com>

	* libs/gst/base/gstbasesrc.c:
	  basesrc: handle reference in set_allocation rather than in prepare_allocation
	  Otherwise we can forget to unref objects in error cases.
	  https://bugzilla.gnome.org/show_bug.cgi?id=736680

2014-09-15 13:06:40 +0300  Sebastian Dröge <sebastian@centricular.com>

	* libs/gst/check/gstcheck.c:
	  check: Use the name parameter of gst_check_setup_src_pad_by_name() and the sink variant
	  This was hardcoded to "sink" / "src" by accident in previous refactoring.

2014-09-10 14:53:00 +0200  Ognyan Tonchev <ognyan@axis.com>

	* gst/gstquery.c:
	  query: add annotations to gst_query_set_nth_allocation_pool()
	  https://bugzilla.gnome.org//show_bug.cgi?id=736424

2014-09-11 09:35:17 +0200  Rémi Lefèvre <remi.lefevre@parrot.com>

	* plugins/elements/gstvalve.c:
	  valve: fix typo in description
	  https://bugzilla.gnome.org/show_bug.cgi?id=736455

2014-08-27 17:06:57 +0530  Ravi Kiran K N <ravi.kiran@samsung.com>

	* plugins/elements/gstoutputselector.c:
	  output-selector: Send all events to active src pad and EOS to all src pads
	  Fixes tests/icles/output-selector-test
	  https://bugzilla.gnome.org/show_bug.cgi?id=729811

2014-09-03 17:38:16 +0100  Tim-Philipp Müller <tim@centricular.com>

	* gst/gstdevicemonitor.c:
	  devicemonitor: fix typo in sample code in docs
	  https://bugzilla.gnome.org/show_bug.cgi?id=735975

2014-08-07 12:18:04 +0200  Thibault Saunier <thibault.saunier@collabora.com>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: Not post BUFFERING message if one of the singlequeue doesn't need it
	  Imagine the following 'pipeline'
	  --------------
	  p1/| 'fullqueue'  |--- 'laggy' downstream
	  ---------  / |              |
	  -| demuxer |   | multiqueue   |
	  ---------  \ |              |
	  p2\| 'emptyqueue' |--- 'fast' downstream
	  --------------
	  In the case downstream of one single queue (fullqueue) has (a lot of) latency
	  (for example for reverse playback with video), we can end up having the other
	  SingleQueue (emptyqueue) emptied, before that fullqueue gets
	  unblocked. In the meantime, the demuxer tries to push on fullqueue, and
	  is blocking there.
	  In that case the current code will post a BUFFERING message on the bus when
	  emptyqueue gets emptied, that leads to the application setting the pipeline state to
	  PAUSED. So now we end up in a situation where 'laggy downstream' is
	  prerolled and will not unblock anymore because the pipeline is set to
	  PAUSED, the fullequeue does not have a chance to be emptied and
	  the emptyqueue can not get filled anymore so no more BUFERRING message
	  will be posted and the pipeline is stucked in PAUSED for the eternity.
	  Making sure that we do not try to "buffer" if one of the single queue
	  does not need buffering, prevents this situtation from happening though it lets the
	  oportunity for buffering in all other cases.
	  That implements a new logic where we need all singlequeue to need
	  buffering for the multiqueue to actually state buffering is needed,
	  taking the maximum buffering of the single queue as the reference point.
	  https://bugzilla.gnome.org/show_bug.cgi?id=734412

2014-08-26 20:14:40 +0200  Arnaud Vrac <avrac@freebox.fr>

	* gst/gstbuffer.c:
	  buffer: do not touch memory tag flag when copying buffer flags
	  The tag memory flag will be set later if the memory is also copied. This
	  patch avoids buffers being freed needlessly in bufferpools.
	  https://bugzilla.gnome.org/show_bug.cgi?id=735574

=== release 1.4.1 ===

2014-08-27 15:03:36 +0300  Sebastian Dröge <sebastian@centricular.com>

	* ChangeLog:
	* NEWS:
	* RELEASE:
	* configure.ac:
	* docs/plugins/inspect/plugin-coreelements.xml:
	* gstreamer.doap:
	* win32/common/config.h:
	* win32/common/gstversion.h:
	  Release 1.4.1

2014-08-27 14:22:21 +0300  Sebastian Dröge <sebastian@centricular.com>

	* po/af.po:
	* po/az.po:
	* po/be.po:
	* po/bg.po:
	* po/ca.po:
	* po/cs.po:
	* po/da.po:
	* po/de.po:
	* po/el.po:
	* po/en_GB.po:
	* po/eo.po:
	* po/es.po:
	* po/eu.po:
	* po/fi.po:
	* po/fr.po:
	* po/gl.po:
	* po/hr.po:
	* po/hu.po:
	* po/id.po:
	* po/it.po:
	* po/ja.po:
	* po/lt.po:
	* po/nb.po:
	* po/nl.po:
	* po/pl.po:
	* po/pt_BR.po:
	* po/ro.po:
	* po/ru.po:
	* po/rw.po:
	* po/sk.po:
	* po/sl.po:
	* po/sq.po:
	* po/sr.po:
	* po/sv.po:
	* po/tr.po:
	* po/uk.po:
	* po/vi.po:
	* po/zh_CN.po:
	* po/zh_TW.po:
	  Update .po files

2014-08-21 14:02:16 +0100  Tim-Philipp Müller <tim@centricular.com>

	* plugins/elements/gstqueue.c:
	  queue: fix race when flush-stop event comes in whilst shutting down
	  Don't re-start the queue push task on the source pad when a
	  flush-stop event comes in and we're in the process of shutting
	  down, otherwise that task will never be stopped again.
	  When the element is set to READY state, the pads get de-activated.
	  The source pad gets deactivated before the queue's own activate_mode
	  function on the source pads gets called (which will stop the thread),
	  so checking whether the pad is active before re-starting the task on
	  receiving flush-stop should be fine. The problem would happen when the
	  flush-stop handler was called just after the queue's activate mode
	  function had stopped the task.
	  Spotted and debugged by Linus Svensson <linux.svensson@axis.com>
	  https://bugzilla.gnome.org/show_bug.cgi?id=734688

2014-08-14 18:53:40 -0300  Thiago Santos <thiagoss@osg.samsung.com>

	* plugins/elements/gstinputselector.c:
	  inputselector: always proxy caps query
	  Otherwise it would only be proxied for the active pad which can lead
	  upstream to use an incompatible caps for the downstream element.
	  Even if a reconfigure event is sent upstream when the pad is activated, this
	  will save the caps reconfiguration if it is already using an acceptable caps.

2014-08-14 14:37:56 +0100  Tim-Philipp Müller <tim@centricular.com>

	* libs/gst/base/gstdataqueue.h:
	  base: and fix build with new g-i again

2014-08-14 14:25:06 +0100  Tim-Philipp Müller <tim@centricular.com>

	* libs/gst/base/gstdataqueue.h:
	  base: remove g-i annotation that makes older g-ir-scanner crash
	  Just remove one skip annotation that causes this:
	  ** (g-ir-compiler:12458): ERROR **: Caught NULL node, parent=empty
	  with older g-i versions such as 1.32.1.

2014-08-13 13:01:23 +0300  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: Only handle flow returns < EOS as errors, not e.g. flushing

2014-08-13 12:40:37 +0300  Sebastian Dröge <sebastian@centricular.com>

	* gst/gstbin.c:
	  bin: Use allow-none instead of nullable until we depend on a new enough GI version

2014-08-13 12:39:47 +0300  Sebastian Dröge <sebastian@centricular.com>

	* gst/gstbin.c:
	  bin: gst_bin_new() can accept NULL as name

2014-08-13 12:37:08 +0300  Sebastian Dröge <sebastian@centricular.com>

	* gst/gstelement.c:
	  element: Clarify docs about gst_element_get_request_pad() and remove deprecation part
	  This function is not really pad or slow for the common case of requesting a
	  pad with the name of the template. It is only slower if you to name your pads
	  directly instead of letting the element handle it.
	  Also there's no reason to deprecate it in favor of a more complicated function
	  for the common case.

2014-08-13 12:20:51 +0300  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstqueue2.c:
	  queue2: Post errors if we receive EOS after downstream reported an error
	  There will be no further data flow that would allow us to propagate the
	  error upstream, causing nobody at all to post an error message.

2014-08-13 12:15:03 +0300  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstqueue.c:
	  queue: Post errors when receiving EOS after downstream returned an error
	  There might be no further data flow that would allow us to propagate the
	  error upstream, causing nobody to post an error at all.

2014-08-13 12:10:39 +0300  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: Post errors ourselves if they are received after EOS
	  After EOS there will be no further buffer which could propagate the
	  error upstream, so nothing is going to post an error message and
	  the pipeline just idles around.

2014-07-27 03:06:16 +0000  Руслан Ижбулатов <lrn1986@gmail.com>

	* gst/gstpoll.c:
	  poll: Prevent false-negative from WAKE_EVENT() on W32
	  SetEvent() seems to not call SetLastError(0) internally, so checking last
	  error after calling SetEvent() may return the error from an earlier W32 API
	  call. Fix this by calling SetlastError(0) explicitly.
	  Currently WAKE_EVENT() code is cramped into a macro and doesn't look to be
	  entirely correct. Particularly, it does not check the return value of
	  SetEvent(), only the thread-local W32 error value. It is likely that SetEvent()
	  actually just returns non-zero value, but the code mistakenly thinks that the
	  call has failed, because GetLastError() seems to indicate so.
	  https://bugzilla.gnome.org/show_bug.cgi?id=733805

2014-07-30 15:46:22 +0300  Mohammed Sameer <msameer@foolab.org>

	* gst/gstbufferpool.c:
	  bufferpool: Add missing error checking to default_alloc_buffer()
	  default_alloc_buffer() calls gst_buffer_new_allocate() but does not check for
	  failed allocation.
	  This patch makes default_alloc_buffer() return an error (GST_FLOW_ERROR) if
	  buffer allocation fails.
	  https://bugzilla.gnome.org/show_bug.cgi?id=733974

2014-07-29 14:21:33 -0300  Thiago Santos <ts.santos@osg.sisa.samsung.com>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: avoid using infinite buffers limit if finite is requested
	  If the current max-buffers limit it infinite and a finite value is
	  requested, switch to the MAX (requested, current-value) to set some
	  limit but not below what we know that we've needed so far.
	  https://bugzilla.gnome.org/show_bug.cgi?id=733837

2014-07-24 22:02:58 +0200  Sebastian Rasmussen <sebras@hotmail.com>

	* gst/parse/grammar.y:
	  parse: Unref reference to enclosing bins
	  Previously all reference to enclosing bins of an element were leaked
	  when doing delaying setting a property.
	  Fixes https://bugzilla.gnome.org/show_bug.cgi?id=733697

2014-07-26 14:42:54 +0100  Tim-Philipp Müller <tim@centricular.com>

	* gst/gst.h:
	  gst: include atomicqueue.h again in gst.h
	  It's a public header of gstreamer core, so #include <gst/gst.h>
	  should make the API available.

2014-07-09 15:48:10 +0200  Srimanta Panda <srimanta@axis.com>

	* plugins/elements/gstfunnel.c:
	  funnel: Fix for racy EOS event handling
	  When eos events are forwarded simultaneouly from two sinkpads on
	  funnel, it doesnot forward the eos to sourcepad. The reason is
	  sticky events are stored after the event callbacks are returned.
	  Therefore while one is about to store the sticky events on the its
	  sinkpad, other sinkpad starts checking for the eos events on all other
	  sinkpads and assumes eos is not present yet.
	  https://bugzilla.gnome.org/show_bug.cgi?id=732851

=== release 1.4.0 ===

2014-07-19 16:46:41 +0200  Sebastian Dröge <sebastian@centricular.com>

	* ChangeLog:
	* NEWS:
	* RELEASE:
	* configure.ac:
	* docs/plugins/inspect/plugin-coreelements.xml:
	* gstreamer.doap:
	* win32/common/config.h:
	* win32/common/gstversion.h:
	  Release 1.4.0

2014-07-19 16:21:20 +0200  Sebastian Dröge <sebastian@centricular.com>

	* po/af.po:
	* po/az.po:
	* po/be.po:
	* po/bg.po:
	* po/ca.po:
	* po/cs.po:
	* po/da.po:
	* po/de.po:
	* po/el.po:
	* po/en_GB.po:
	* po/eo.po:
	* po/es.po:
	* po/eu.po:
	* po/fi.po:
	* po/fr.po:
	* po/gl.po:
	* po/hr.po:
	* po/hu.po:
	* po/id.po:
	* po/it.po:
	* po/ja.po:
	* po/lt.po:
	* po/nb.po:
	* po/nl.po:
	* po/pl.po:
	* po/pt_BR.po:
	* po/ro.po:
	* po/ru.po:
	* po/rw.po:
	* po/sk.po:
	* po/sl.po:
	* po/sq.po:
	* po/sr.po:
	* po/sv.po:
	* po/tr.po:
	* po/uk.po:
	* po/vi.po:
	* po/zh_CN.po:
	* po/zh_TW.po:
	  Update .po files

2014-07-19 12:16:58 +0200  Sebastian Dröge <sebastian@centricular.com>

	* po/da.po:
	* po/sv.po:
	  po: Update translations

2014-07-17 15:53:53 +0200  Thibault Saunier <tsaunier@gnome.org>

	* libs/gst/base/gstbaseparse.c:
	  baseparse: Return FLOW_FLUSHING when pushing a frame on a pad that has been flushed
	  When going to READY, it is possible that we are still pusing a frame but that
	  our srcpad has already been set to flushing. In that case we should not
	  post any error on the bus but instead cleanly return FLOW_FLUSHING.
	  https://bugzilla.gnome.org/show_bug.cgi?id=733320

2014-07-17 07:07:36 +0200  Edward Hervey <edward@collabora.com>

	* plugins/elements/gsttypefindelement.c:
	  typefindelement: Propagate input buffer PTS and DTS
	  The initial buffers (that were used for timestamping) might have PTS
	  and DTS set. In order to forward those properly, get the initial
	  PTS/DTS from the adapter and set them on the reconstructed output
	  buffer.
	  https://bugzilla.gnome.org/show_bug.cgi?id=733291

2014-07-12 17:01:23 +0200  Sebastian Rasmussen <sebras@hotmail.com>

	* gst/gstdebugutils.c:
	  debugutils: Unref pad template after use
	  Fixes https://bugzilla.gnome.org/show_bug.cgi?id=733121

2014-07-14 18:10:45 -0300  Thiago Santos <ts.santos@sisa.samsung.com>

	* gst/gst.c:
	  gst: init taglist gtype to use it in gstvalue
	  Otherwise it will have a 0 value and GstTagList won't be found
	  for GstValue functions (serialization/deserialization)
	  https://bugzilla.gnome.org/show_bug.cgi?id=733131

=== release 1.3.91 ===

2014-07-11 10:46:01 +0200  Sebastian Dröge <sebastian@centricular.com>

	* ChangeLog:
	* NEWS:
	* RELEASE:
	* configure.ac:
	* docs/plugins/inspect/plugin-coreelements.xml:
	* gstreamer.doap:
	* win32/common/config.h:
	* win32/common/gstversion.h:
	  Release 1.3.91

2014-07-11 10:41:20 +0200  Sebastian Dröge <sebastian@centricular.com>

	* po/af.po:
	* po/az.po:
	* po/be.po:
	* po/bg.po:
	* po/ca.po:
	* po/cs.po:
	* po/da.po:
	* po/de.po:
	* po/el.po:
	* po/en_GB.po:
	* po/eo.po:
	* po/es.po:
	* po/eu.po:
	* po/fi.po:
	* po/fr.po:
	* po/gl.po:
	* po/hr.po:
	* po/hu.po:
	* po/id.po:
	* po/it.po:
	* po/ja.po:
	* po/lt.po:
	* po/nb.po:
	* po/nl.po:
	* po/pl.po:
	* po/pt_BR.po:
	* po/ro.po:
	* po/ru.po:
	* po/rw.po:
	* po/sk.po:
	* po/sl.po:
	* po/sq.po:
	* po/sr.po:
	* po/sv.po:
	* po/tr.po:
	* po/uk.po:
	* po/vi.po:
	* po/zh_CN.po:
	* po/zh_TW.po:
	  Update .po files

2014-07-11 08:51:08 +0200  Sebastian Dröge <sebastian@centricular.com>

	* po/da.po:
	* po/vi.po:
	  po: Update translations

2014-07-05 18:29:29 +0200  Sebastian Rasmussen <sebras@hotmail.com>

	* docs/libs/gstreamer-libs-docs.sgml:
	* docs/libs/gstreamer-libs-sections.txt:
	* gst/gstcaps.h:
	* gst/gstdevice.c:
	* gst/gstdeviceprovider.c:
	* gst/gstdeviceproviderfactory.c:
	* gst/gsttoc.h:
	* gst/gstvalue.c:
	* libs/gst/check/gstcheck.c:
	* libs/gst/net/gstnetaddressmeta.c:
	* libs/gst/net/gstnetaddressmeta.h:
	  docs: Fix documentation typos and inconsistencies
	  * GstGlobalDeviceMonitor was renamed to GstDeviceMonitor
	  * Expand GST_MESSAGE_DEVICE to the full enum value names
	  * Correct the incorrect references to the GstDeviceProvider interfaces
	  * Describe caps arguments for gstcheck interface
	  * Add missing docs for GstNetAddressMeta and its add function
	  * Add docs for toc helper macros
	  * Avoid refering to GstValueList type as done elsewhere
	  Fixes https://bugzilla.gnome.org/show_bug.cgi?id=732786

2014-07-05 17:13:21 +0200  Sebastian Rasmussen <sebras@hotmail.com>

	* docs/gst/gstreamer-sections.txt:
	* docs/libs/gstreamer-libs-sections.txt:
	  docs: Cleanup interface references in docs
	  * Delete references to removed interfaces
	  * Add missing documentation sections
	  * Fix duplicate interface references for GstDevice
	  Fixes https://bugzilla.gnome.org/show_bug.cgi?id=732786

2014-07-08 11:17:41 +0200  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstfilesrc.c:
	* plugins/elements/gsttee.c:
	* tools/gst-launch.1.in:
	  docs: There is no decodebin2 anymore, don't pretend otherwise

2014-07-07 16:14:32 -0300  Thiago Santos <ts.santos@sisa.samsung.com>

	* plugins/elements/gstfdsrc.c:
	  fdsrc: fix error setting when uri is invalid
	  Elements should always set the GError

2014-07-06 12:13:04 +0100  Tim-Philipp Müller <tim@centricular.com>

	* libs/gst/check/gstcheck.h:
	  libs: gstcheck: check that mutex is locked before g_cond_wait*() is called
	  Sanity check to catch problems in unit test.

2014-07-06 12:12:20 +0100  Tim-Philipp Müller <tim@centricular.com>

	* libs/gst/check/gstcheck.h:
	  libs: gstcheck: init and clear global mutex and cond variables

2014-07-06 12:09:31 +0100  Tim-Philipp Müller <tim@centricular.com>

	* tests/check/gst/gstpoll.c:
	  tests: fix locking in gstpoll unit test
	  The mutex needs to be locked when g_cond_wait*() is
	  called.

2014-07-05 16:24:18 +0100  Matthieu Bouron <matthieu.bouron@collabora.com>

	* scripts/gst-uninstalled:
	  gst-uninstalled: add video and base library paths from -bad
	  https://bugzilla.gnome.org/show_bug.cgi?id=732770

2014-07-04 19:40:28 +0100  Tim-Philipp Müller <tim@centricular.com>

	* tools/gst-inspect.c:
	  tools: suppress GLib warnings when gst-inspecting deprecated properties
	  GLib in git will spew a g_warning() when a property marked as
	  deprecated via param spec flags is accessed. Suppress this by
	  setting the appropriate environment variable.

2014-07-03 10:11:02 +0200  Sebastian Dröge <sebastian@centricular.com>

	* gst/gstmessage.h:
	  message: Work around g-i/pygobject/gjs bug with ~0 in enums
	  GST_MESSAGE_ANY was considered a long by pygobject and gjs, and thus
	  couldn't be used in gst_bus_poll() and similar APIs as they expect an
	  int-typed enum.
	  Just use 0xffffffff instead for now.
	  https://bugzilla.gnome.org/show_bug.cgi?id=732633

2014-07-02 08:41:18 +0100  Tim-Philipp Müller <tim@centricular.com>

	* tests/check/gst/gstbufferlist.c:
	  tests: don't use post-GLib 2.32 API in bufferlist test
	  g_ptr_array_insert() is GLib >= 2.40

2014-07-01 12:22:56 +0200  Göran Jönsson <goranjn@axis.com>

	* gst/gstpad.c:
	  pad: Don't unlock while iterating over all sticky events for removal
	  Otherwise we might end up getting the event removed from elsewhere
	  at the same time while we're unlocked for g_object_notify().
	  https://bugzilla.gnome.org/show_bug.cgi?id=732556

2014-07-01 19:17:11 +0200  Sebastian Dröge <sebastian@centricular.com>

	* plugins/elements/gstidentity.c:
	  identity: Proxy the accept-caps query
	  We always work in passthrough mode so there's no point in doing
	  something more clever in basetransform. Also the basetransform
	  code leads to problems with incomplete caps and downstream
	  elements that use GST_PAD_FLAG_ACCEPT_INTERSECT.
