Bug#793316: [debian-mysql] Bug#793316: transition: mysql-5.6
Excerpts from Emilio Pozuelo Monfort's message of 2015-07-23 01:59:15 -0700:
> On 22/07/15 21:24, Andreas Beckmann wrote:
> > Package: release.debian.org
> > User: release.debian.org@packages.debian.org
> > Usertags: transition
> > Severity: normal
> > X-Debbugs-Cc: pkg-mysql-maint@lists.alioth.debian.org
> > Control: block -1 with 793314 793315
> >
> > On behalf of the MySQL maintainers I'm filing this transition bug.
> > Please keep the list Cc:ed on replies.
> >
> > The core packages involved here are mysql-5.5, mysql-5.6, mariadb-10.0.
> > In order for mysql-5.6 to enter testing mysql-5.5 has to leave and
> > mariadb-10.0 has to migrate at the same time.
>
> Didn't we agree that we would release Stretch with only mariadb? When do you
> plan to start working on that so we can drop mysql-* from testing?
Please do read up on the differences. MySQL 5.6 and MariaDB 10.0 are
already a little bit incompatible, but 5.7 will introduce some features
that MariaDB will likely be chasing for some time.
https://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html
Thus far I think the main feature of MariaDB is "it's not made by
Oracle". However, frankly, Oracle have been helping maintain MySQL more
than MontyProgram/SkySQL (easy to be above 0) and have demonstrated that
they are in fact very interested in doing what is needed to keep MySQL
in Debian. Otto K., a MariaDB community member, has done an amazing
job at improving MariaDB and keeping it in some ways ahead of the MySQL
packaging, so I think the two databases are neck and neck at this point.
I'd be interested to hear the security team's impressions on how shipping
micro releases of MySQL has gone for them. They've been doing most if not
all of the work, and I haven't seen bug reports flying in about those
updates, so I suspect our primary gripe about MySQL may actually be no
big deal. Sure they have a _ridiculous_ policy about not telling us what
the actual security problems were. But they also have quite impressive
policies on not breaking things in micro releases.
So, shipping two, or three, is a drain on resources, but there seem to
be enough developers to commit to maintaining both. Perhaps we should
just keep shipping both.
Also sorry Percona, I've lost track of you, your Galera work is vital
to OpenStack, so I hope you'll keep maintaining things as well. In the
past you were right there with Oracle supporting your fork. :)
Reply to: