Comment 8 for bug 1528583

Revision history for this message
Robie Basak (racb) wrote :

I've uploaded an initial cut of the proposed 5.7 packaging to our PPA: https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mysql-5.7/+packages and my current work tree (still being rebased) is available at https://git.launchpad.net/~racb/ubuntu/+source/mysql-5.7/log/?h=5.7v5ubuntu_dev2

I'd appreciate anyone who can test these packages to help inform the release team about the regression risk for this FFe.

Here are my thoughts on what will be valuable to test and what probably doesn't need testing.

What doesn't need testing first. This is about the packaging. We generally trust upstream's QA process for MySQL itself as they have a good track record on this. So once MySQL is running, we expect it to work. So no need to test in detail that MySQL is functioning as expected, expect where functionality interacts with packaging. Testing that mysql-files and mysql-keyring are working is good, as is that plugins work, since that interacts with how we ship the files. Testing the functionality of the SELECT statement probably isn't, since that's a core thing that is unlikely to be regressed by packaging.

Note that migrating from MariaDB to MySQL is not expected to work currently unless you manage this process manually yourself.

Next, specific paths to test. We want to check that the package works both when installed freshly on Xenial and also when upgrading from Trusty or Wily. Other things that could influence success are how the user installed on the previous release (eg. which packages were installed and whether and how configuration files in /etc were changed - see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813413 for an example of a failure case in this area; this one is known to not be fixed yet as we don't have a good answer).

Previous upgrade paths might also change behaviour - that is, the state of /var/lib/mysql as it ended up by use of previous MySQL packaging releases.

If you can help out with testing, please report back in this bug detailing exactly what you tested and what your results are. Please report both success and failure. Thanks!