-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 moin,
to sum things up: * mariadb-5.5 within testing * mariadb-10.0 within experimental * mysql-5.5 within testing * mysql-5.6 within experimental * percona-xtradb-cluster-server-5.5 within sid - From my point of view we should not talk about percona-xtradb-cluster-server as a mysql replacement as it does not provide any libs nor -dev packages and will always be a very close relative to mysql. Although my opinion is to let Debian users decide which fork to use I can fully understand release/security team concerns. So which way to go? * stick with mysql and start transition -> 5.6 * replace mysql with mariadb and start transition -> 10.0 * create an ecosystem where several forks may live side by side pkg-mysql is unfortunately not one of the strongest teams in terms of manpower, but even though we tried to come up with a solution to fullfil anybodys wishes. As the transition timeframe is quite close we need a decision! This decision should be done by the release team agreed together with your collegues at ubuntu/canonical as we should definately *not* fork this decision! Maybe the tech-ctte could also be involved? Cheers B -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iEYEARECAAYFAlP9uRMACgkQABMWRpwdNunOagCgqxr3ArsWVvo4dn1Rv727A+tW dEcAoLXdpY9zVYupC7kuMOMv28LoqTsr =AbEO -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53fdb913.3090...@boschman.de
