[debian-mysql] Justification for MySQL 5.5.30 going into unstable now

[Clint Byrum]

Hello Release team.

MySQL in testing is currently 5.5.28.
MySQL in unstable is currently 5.5.29.
MySQL upstream has released 5.5.30.

MySQL 5.5.30 is the current "stable" release of MySQL. We can anticipate
5.5.31 very soon. I suspect there will be security fixes in that release,
although Oracle will not tell me either way. Because we know that there
will likely be more security problems found, and that we will likely
have to ship subsequent MySQL 5.5 releases in stable-security, I would
like to propose that we do everything we can to ship the latest release
of MySQL with wheezy.

I know that this is not Debian's normal preference, but Oracle has
left us little choice. We have packagers working on bringing MariaDB
to Debian, and other alternatives exist, but MySQL is so popular that
I feel compelled to keep it as well maintained as we can.

So, I have prepared 5.5.30 packages and done light testing of them for
the last week. I would like to upload these to unstable. These packages
also fix one RC bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698068

The other remaining RC bug is a bit more complicated and somewhat lower
priority, and I suggest we release without fixing it (or delay the
release until MySQL upstream fixes it):

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699886

So, I am asking for advice. Release team, should I go ahead with this
upload and can I reasonably expect a freeze exception?

The packaging diff is summed up in these two commits:

http://anonscm.debian.org/viewvc/pkg-mysql?view=revision&revision=2216
http://anonscm.debian.org/viewvc/pkg-mysql?view=revision&revision=2217

Thank you for your time and efforts!