Re: [debian-mysql] Backporting MySQL?
- To: Dominic Hargreaves <firstname.lastname@example.org>
- Cc: debian-backports <email@example.com>, Debian MySQL Maintainers <firstname.lastname@example.org>
- Subject: Re: [debian-mysql] Backporting MySQL?
- From: Lars Tangvald <email@example.com>
- Date: Mon, 7 Nov 2016 12:49:07 +0100
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <20161031175539.GF6016@urchin.earth.li>
- References: <20160624142717.GZ5873@urchin.earth.li> <email@example.com> <20160624155058.GA5873@urchin.earth.li> <firstname.lastname@example.org> <20160625171648.GH5873@urchin.earth.li> <20160627195633.GL5873@urchin.earth.li> <email@example.com> <20161018092257.GT21476@urchin.earth.li> <20161028145743.GC6016@urchin.earth.li> <firstname.lastname@example.org> <20161031175539.GF6016@urchin.earth.li>
On 10/31/2016 06:55 PM, Dominic Hargreaves wrote:
We consider it stable. 5.7 has been in Ubuntu since the 16.04 release,
so we've had time to see it in use, fix issues etc.
We do have the 5.7.16 security update waiting for an upload to unstable,
though, and that should be included.
My main concern is having a security-supported backport of MySQL > 5.5.
At the moment the best of achieving that without the additional risk of a
major version upgrade is to carry on using 5.6, so if you would be able
to continue to support that for a while that'd be much appreciated, but
I realise this isn't sustainable long-term.
From your side, is there more work needed on mysql-5.7 in unstable before
you would consider it suitable for backporting to stable?