Comment 27 for bug 1427406

After discussing my concerns with dannf and rbasak on irc, we have come to the following:

- We are aware of this issue, and are making reasonable efforts to ensure that users are not impacted. However, as highlighted by point (5) below, there may be circumstances in which we have to regress this fix in order to ensure a security patch will be applied.

- dannf's team has commitment from Oracle to fix broken archs in some future version
- patches are only applied to affected archs
- MySQL updates are usually available before Oracle's quarterly security notice is published
(Quarterly security notice can be viewed here: http://www.oracle.com/technetwork/topics/security/alerts-086861.html )

1) dannf's team will figure out how to be notified of a new micro release
2) dannf's team will update a PPA w/ the new micro release before quarterly security notice (~6 weeks generally, but can be immediate)
* In the event where a new MySQL version is published at the same time as the quarterly security notice, dannf's team will update the PPA with updated patches no more than 2 working days after publication
3) dannf's team will test the updated PPA on arm64 (ppc64el will not be explicitly tested)

4) security team will pull updated patches from ppa when preparing security updates. Security updates will not be tested on affected architectures

5) Security updates will not be held back if there is a problem with "the patch". If necessary, arm64/ppc64el users will be regressed by the security team issuing an update with the patch dropped. If the patch is dropped, a notice will be added to the Ubuntu Security Notice.