Changes to make MySQL vs. MariaDB less confusing

[Johannes Lips]

On Fri, Aug 23, 2013 at 9:40 AM, James Hogarth <james.hogarth at gmail.com>wrote:

> On 22 August 2013 08:27, Bjorn Munch <bjorn.munch at oracle.com> wrote:
>
>>
>> Yes we are! Sorry for the long silence. The window for F19 closed so
>> it became less urgent, then I had vacation, was sick, then others here
>> were on vacation but we're all here now and I shall be uploading new
>> packages with MySQL 5.6.13 very soon. They are already ready
>> internally, but I need to do some final checks and a scratch build. I
>> was indeed planning to do that today anyway.
>>
>> I will get back with more details later.
>>
>>
> It's this sort of behaviour that leads many of us to want to wash our
> hands of Oracle in the first place...
>
Sorry to say, but to me it rather sounds just plain human.


>
> As for the 'window for F19' well you've missed the window for F20 now as
> well ...
>
> However that is somewhat of a moot point given that (and the AOO issues
> are similar but let's stay focused on mysql/mariadb) things like spec
> files, package reviews and so on don't need a release to target anyway -
> they just need bugzilla tickets and builds in koji following the standard
> packaging guidelines that everyone - big company or little individuals -
> need to follow.
>
> Once things are building cleanly there and package review is passed (and
> any outstanding conflict questions are dealt with) then fine look at adding
> it as a feature for a future Fedora - but that is a long way off at this
> point still it seems.
>
> Frankly I'm still of the opinion the Oracle distribution of the MySQL
> based server should be dropped entirely... If Oracle want 'community-mysql'
> to exist for Fedora and want to maintain it themselves then they can set up
> their own repositories on their own infrastructure and these
> compatibilities issues with Fedora can be removed entirely as a result.
>
> As for an upgrade of community-mysql from 5.5 to 5.6 that should probably
> be discussed or be considered as a feature in case of knock on issues with
> respect to F18 users upgrading (didn't the obsolete for mariadb only cover
> < 5.5?) plus the loss of file level compatibility for someone to make a
> switch between community-mysql and mariadb at their choosing... plus
> there's a lot of non-backwards compatible changes that people need to be
> aware of from 5.5 to 5.6:
>
> http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html
>
>
>
>
>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20130823/69747572/attachment.html>