(Creation) |
m (Add this wiki page to MariaDB category) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
== Summary == | == Summary == | ||
Update of MySQL ( community-mysql package) in Fedora from 5.7 to 8.0 version. | Update of MySQL ( community-mysql package) in Fedora from 5.7 to 8.0 version. | ||
[[Category:Package MariaDB]] | |||
== Owner == | == Owner == | ||
| Line 20: | Line 21: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1582618 #1582618] | ||
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/174 #174] | |||
== Detailed Description == | == Detailed Description == | ||
| Line 30: | Line 32: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
I'm cooperating with the | I'm cooperating with the upstream to bring the latest stable software to Fedora users. | ||
== Scope == | == Scope == | ||
| Line 41: | Line 43: | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Release engineering: [https://pagure.io/releng/ | * Release engineering: [https://pagure.io/releng/issue/7486 Releng issue number 7486] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 55: | Line 57: | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
The 'libmysqld' embedded server library has been removed by upstream. | The 'libmysqld' embedded server library has been removed by upstream. (Though, applications requiring 'libmysqld' can be (re)built against `mariadb-embedded-devel`, which Provides `mysql-embedded-devel` and ships a `libmysqld.so` symlink to `libmariadbd.so.*`.) | ||
Downgrade from MySQL 8 to MySQL 5.7 is not supported. | |||
== How To Test == | == How To Test == | ||
| Line 90: | Line 94: | ||
== Documentation == | == Documentation == | ||
Upgrading and incompatibilities: https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html | |||
Upgrade startegy: https://dev.mysql.com/doc/refman/8.0/en/upgrading-strategies.html | |||
== Release Notes == | == Release Notes == | ||
| Line 100: | Line 104: | ||
Overall overview of the changes in 8.0: https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html | Overall overview of the changes in 8.0: https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html | ||
[[Category: | [[Category:ChangeAcceptedF29]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 15:59, 19 February 2020
MySQL 8
Summary
Update of MySQL ( community-mysql package) in Fedora from 5.7 to 8.0 version.
Owner
- Name: Michal Schorm
- Email: mschorm@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 29
- Last updated: 2020-02-19
- Tracker bug: #1582618
- Release Notes tracking: #174
Detailed Description
Update of MySQL package in Fedora from 5.7 version to 8.0 version.
Benefit to Fedora
I'm cooperating with the upstream to bring the latest stable software to Fedora users.
Scope
- Proposal owners:
- Release MySQL 8.0.11 to Rawhide (done)
- Check software that requires community-mysql package (done, only mysql-connector-odbc)
- Gather user input on the changes between mysql 5.7 and 8.0
- Other developers: N/A (not a System Wide Change)
- Release engineering: Releng issue number 7486 (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
The 'libmysqld' embedded server library has been removed by upstream. (Though, applications requiring 'libmysqld' can be (re)built against mariadb-embedded-devel, which Provides mysql-embedded-devel and ships a libmysqld.so symlink to libmariadbd.so.*.)
Downgrade from MySQL 8 to MySQL 5.7 is not supported.
How To Test
Usual testing as when upgrading between major MySQL versions.
Test that all other software runs well with MySQL 8. Report any issues, so I can reach the different upstreams and check if they plan update their software to support MySQL 8 and when.
User Experience
The users will have to migrate their applications and databases, if the y want to use MySQL 8.
If the users want to stick with MySQL 5.7 for a little longer, I'm providing COPR repo with MySQL 5.7 built from f28 branch for Rawhide.
Also, module with MySQL 5.7 is planned.
Dependencies
mysql-connector-odbc
- also maintained by me
- currently FTBFS against the MySQL 8.0.11, working on the fix. However for MariaDB there is mariadb-connector-odbc, so users don't depend on this piece of software.
There may be more software, which does not support MySQL 8 yet. For such occurences, COPR repo with MySQL 5.7 was created.
Contingency Plan
The COPR repository until F29 freeze seems enough to me. For F29, there should be a module available with MySQL 5.7 to cover users that can't / don't want to upgrade.
- Contingency mechanism: COPR and Module with MySQL 5.7 available
- Contingency deadline: beta freeze
- Blocks release? N/A (not a System Wide Change)
- Blocks product? N/A (not a System Wide Change)
Documentation
Upgrading and incompatibilities: https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html
Upgrade startegy: https://dev.mysql.com/doc/refman/8.0/en/upgrading-strategies.html
Release Notes
Release notes for each release: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/
Overall overview of the changes in 8.0: https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html