[debian-mysql] MySQL in Jessie

[Matt Griffin]

Great suggestions by all. I'd prefer to wait for James and Robie to chime
in, as they are both away at the moment, to make decisions on approaches
here. They have been making great progress on solving the challenges of
having the three options (MySQL, Percona Server, and MariaDB) all live
"side-by-side" and giving users choice.
So if there's not a need to make a decision today or this week, waiting to
hear their opinions would be advised.

Best,
Matt



On Wed, Aug 27, 2014 at 2:47 PM, Otto Kekäläinen <otto at seravo.fi> wrote:

> Hello!
>
> 2014-08-27 13:55 GMT+03:00 Bjoern Boschman <bjoern at boschman.de>:
> >
> > Although my opinion is to let Debian users decide which fork to use I
> > can fully understand release/security team concerns.
>
> I also think there are fairly good reasons to provide multiple
> versions and let users decide. Also, personally I would also feel very
> depressed if my work on MariaDB packaging for Debian that I've done
> for the last 1,5 years would turn out to be useless.. I also have the
> feeling and experience that a lot of people want to see MariaDB
> finally enter Debian. The ITP was filed already in 2010[1] but only
> about a year ago it actually was closed, while during that time every
> other major distro has included MariaDB  - and by now many big distros
> have even decided to default to MariaDB over MySQL. We can for sure
> assume that there is user demand for this package in Debian to
> motivate that it should be available.
>
>
> > 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
>
> There is one more option to this list: stick with what is in Debian
> testing now.
>
> The stuff that is in testing has been agreed on internally by the
> pkg-mysql team and it has passed all the QA and there is assurance
> that it works well. Yes, it's not the fancy new stuff, but then again
> Debian is known for being very stable (and slow to introduce new
> stuff) and shipping mysql-5.5 and mariadb-5.5 parallel for the
> duration of one release would fit Debian well.
>
> Also keep in mind that the 5.5 versions aren't going to go sour in our
> hands. They are shipped in many other long term releases of other
> major distros and are likely to get security updates for a long time.
>
>
> > 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!
>
> Ubuntu 14.04 shipped with mysql-5.5 in main and mariadb-5.5, mysql-5.6
> and percona-xtradb-cluster in universe. I am not saying this is
> optimal, but it can and is a source of security update releasing
> people if a Debian release is in sync.
>
> If we really only want to pick just one flavour, the pkg-maint team
> will probably not be able to agree and it would be better resolved by
> maybe the tech-ctte.
>
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565308
>
> _______________________________________________
> pkg-mysql-maint mailing list
> pkg-mysql-maint at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20140827/a181edb6/attachment.html>