Comment 27 for bug 1700373

There has been no further feedback from other members of the SRU team (neither in this bug nor in the ubuntu-release@ ML thread). In order to make progress I'm proceeding with my decision as the position of the SRU team. We can re-evaluate if new technical considerations come to light, or if others in the SRU team or TB want to interject.

On this basis we are not proceeding with xnox's backports for Xenial and Yakkety, since they change more than just the microcode.

xnox's Zesty upload I reluctantly accept. It doesn't introduce any packaging changes (as it's close enough to the latest in Artful and in Debian sid) so I concede that it cannot introduce any additional regression risk over just a blob update. It is stylistically a backport though (eg. changelog, version string), rather than a blob update, so will end up looking different from Xenial and Yakkety if X and Y do get blob-only updates in the end. I don't like this, but as xnox has pointed out pushing the update to Zesty will help with phasing the update to mitigate risk to users, so I am accepting it.

Please note that packages in Ubuntu are team maintained. As xnox has unassigned himself for now, I'll seek another developer to prepare the updates for Xenial and Yakkety. I would do it myself, but I'm not supposed to wear both hats.

Once we have another developer looking at this, we can examine the Trusty situation and make a decision about Trusty.