Patch Merging Status

[Richard Purdie <richard.purdie@linuxfoundation.org>]

I'm faced with a bit of a dilemma with the number of queued changes. I'm
not very happy with as many updates right on the release freeze deadline
and I know this is causing problems for downstream trees like meta-oe
too.

I believe the testing done has found the problematic changes in the
branch (alsa-utils, xserver-xorg and automake for example) and that
we're in a reasonable state to merge these and I appreciate the work
Saul and others have done in stabilising and testing the changes. I
appreciate meta-oe needs more time to test and integrate these though.

One idea would be to feed these in though smaller sets of updates but
since they've been tested as a unit, I don't really want to do this
since I don't have a good feel for any interdependencies.

I'm therefore going to:

a) Pull in fixes and other pending patches other than the big block of
updates now. I've gone ahead and done this.

b) Put the updates on master-next for oe-core. Unless serious issues are
uncovered, these will merge on Wednesday.

This should give everyone the time needed to allow a smooth merge of the
changes and gives room for some further testing.

I should mention this totally screws up Yocto's stabilisation, QA and
other plans since this is going to change timings or workflows. I'm
making the decision knowing that and tending towards breaking the
workflows and keep the original schedule.

Cheers,

Richard