Oops, forgot to include debian-release in the response. Excerpts from Clint Byrum's message of 2014-09-13 19:35:51 -0700: > Excerpts from Jonathan Wiltshire's message of 2014-09-13 15:01:54 -0700: > > On 2014-08-26 11:27, Colin Charles wrote: > > > Upstream will publish security releases for many years to come -- it > > > is the choice of Red Hat Enterprise Linux 7, so the commitment is > > > there > > > > Can you quantify this? I mean, did anyone actually ask upstream what > > their support commitment is going to be? > > > > Colin is upstream, and while he didn't make it a point to speak with the > voice of MontyProgram, I believe he does. > > > >> However, newer is always newer, so shipping MariaDB 10.0 would be nice > > >> if we have time to finalize it after it comes out from the NEW queue.. > > >> > > > > > > I agree. > > > > 10.0 left NEW on 26th August. Since then, it hasn't been uploaded to > > unstable, though I do see a version on mentors from yesterday. > > > > It has the following problems: > > > > - lintian error build-depends-on-obsolete-package > > - rewrites changelog history > > > > It's past the end of transitions for Jessie. Does moving from MariaDB > > 5.5 to 10.0 in Jessie have any transition implications? There's at least > > one symbol that goes away completely. > > > > AFAIK, there aren't any packages that depend on libmariadbclient. The > biggest thing is that 10.0 is not guaranteed to be data-compatible with > MySQL 5.5, so care needs to be taken that there aren't any cases where > data from MySQL might be converted forward to MariaDB 10.0 leaving the > user unable to move back to MySQL.
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
