[debian-mysql] mysql-defaults into unstable?

[Otto Kekäläinen]

Hello!

2016-07-21 23:06 GMT+03:00 Robie Basak <robie.basak at ubuntu.com>:
>> My suggestion:
>> - upload mariadb-10.0 now
>> - upload mysql-5.7 next week
>> - upload mysql-defaults the week after that
>
> I think this plan will be fine for Debian. Thank you for putting it
> forward.

Due to sickness and too much other work etc this got a bit delayed, so
the weeks didn't go as planned, but I have now uploaded mysql-defaults
to unstable and a new mariadb-10.0 and mariadb-connector-c that fixes
some bugs that were discovered when the packages were in experimental.

I'll wait a bit that all Debian QA systems update and that there are
no regressions. After that I'll re-post our debian-devel@ message
shortened to debian-devel-announce@ so that people can start updating
the dependant packages. Then we should wait to allow maintainers to
report if they come across some regressions. Some time in September we
should then start mass bug filing. Do you think we should also try to
get a new rule into Lintian about this? Then packages that want to
depend explicitly on non-default can add a Lintian exception to
document why they don't depend on the mysql-defaults provided package,
and any new package maintainer would automatically see the info about
the mysql-defaults usage policy, so the we are less likely to need to
manually file new bugs in the future?

> I'm still not sure what to do in Ubuntu, but we can figure it out based
> on this timetable for Debian.

Ubuntu freeze is tomorrow. I think it is OK and safe to import
everything in unstable at the moment. The transition in the dependant
packages has not really started yet, so nothing affects Ubuntu in that
regard yet. This will have an effect on Ubuntu in the yakkety+1
release, and I suggest we devote an UDS session to this topic. But
there is plenty of time before yaketty+1. Let's now focus on getting
everything smooth in Debian first.

- Otto