An Ubuntu developer could try and get a micro release exception in place for MySQL, but as I say this is a MySQL-specific problem.
Canonical cannot trump Ubuntu policy.
An Ubuntu developer could try and get a micro release exception in place for MySQL, but as I say this is a MySQL-specific problem.
Canonical cannot trump Ubuntu policy.
Were talking v5.0.30 -> v5.0.31 here (these aren't the actual versions as I don't have them in front of me).
Also it says in our support contract what the policy is. We no longer have any support contract - waste of money.
Policies are ultimately managed by the Technical Board and the Community Council, both of which have members who are not Canonical employees.
Mark Shuttleworth does have ultimate executive rights to do anything he wants, and he does own Canonical. So yes, Mark can set whatever policy he wants. But his use of this veto/executive ability is generally documented and he doesn't use it all that much. Certainly not in the details of MySQL and stable release updates.