However, one package has not yet been updated, and we should note the
following:

** gst-plugins-good is not updated **
** gst-plugins-bad should not be updated until we can update gst-plugins-good
**

The problem with gst-plugins-good 0.10.16 is that many of our changes to v4l2src
did not apply cleanly, and I didn't have time to forward-port this work at the
moment. Last time I did it it wasn't a trivial task.

Details
As we've just frozen for a release, I thought we might want to consider
re-basing to the latest open-source components so we can work out any kinks
during the next development cycle.

Attached are patches that upgrade most open-source components to their latest
versions, including:

However, one package has not yet been updated, and we should note the
following:

** gst-plugins-good is not updated **
** gst-plugins-bad should not be updated until we can update gst-plugins-good
**

The problem with gst-plugins-good 0.10.16 is that many of our changes to v4l2src
did not apply cleanly, and I didn't have time to forward-port this work at the
moment. Last time I did it it wasn't a trivial task.

You'll notice that our release notes are mostly generated from tracker items,
and since this is a tracker item I would expect it to get included during the
next release cycle -- not sure that the release notes need to be actively
matinained between cycles if there are trackers for everything.

Regarding pango, yes, this is a new feature that doesn't build as we are missing
underlying support libraries. If you leave it enabled, I get

checking for PANGO... no
no
configure: No package 'pango' found
No package 'pangocairo' found
checking for PANGOCAIRO_1_15_4... configure: error: Package requirements
(pangocairo &gt;= 1.15.4) were not met:

No package 'pangocairo' found

As a rule of thumb we don't really want add any more dependences on support
libraries unless absolutedly necessary. I added it to the patch.