Latest revision as of 06:45, 12 February 2021

MariaDB 10.5

Summary

Update of MariaDB ('mariadb' package) in Fedora from 10.4 to 10.5 version.

Owner

Name: Michal Schorm
Email: mschorm@redhat.com
Release notes owner:

Current status

Targeted release: Fedora 34
Last updated: 2021-02-12
FESCo issue: #2499
Tracker bug: #1902800
Release Notes tracking: #608

Detailed Description

Update of MariaDB package in Fedora from 10.4 version to 10.5 version.

Benefit to Fedora

I'm cooperating with the upstream to bring the latest stable software to Fedora users.

10.5 series introduces number of enhancements, which cannot be found in previous series. Overview of the new features can be found here: https://mariadb.com/kb/en/changes-improvements-in-mariadb-105/

Scope

Proposal owners:
- Prepare MariaDB 10.4 as a module for Rawhide and atleast one stable Fedora release (done)
  so users which want to stay on the current release have the possibility.
  This also serve as a failover mechanism in case of issues with the 10.5.
- Prepare MariaDB 10.5 as a module for Rawhide and atleast one stable Fedora release (done)
  so users can test the 10.5 in advance. (installing 10.5 module on already stable release)
  This also serve as a upgrade path - users can install 10.5 module on Fedora release which have 10.4 in base; and then upgrade to 10.5 module on a Fedora release which will have 10.5 in base.
- Release MariaDB 10.5 to Rawhide (done; 10.5 modules needs testing first, I got first positive responses)
- Check software that requires or depends on 'mariadb' or 'galera' package for incompatibilities
  This shouldn't be an issue in general, as vast majority of the software requires client library, provided by "mariadb-connector-c" package, which won't change. (done; 'amarok' package)
- Gather user input on the changes between MariaDB 10.4 and 10.5

Other developers: N/A (not a System Wide Change)

Release engineering: (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 MariaDB client library is compatible, so the shouldn't be any issues and / or need for rebuild of dependent packages.

UPDATE (10/2020)

MariaDB 10.5 modules are now available for Fedora Rawhide, Fedora 33, Fedora 32 and Fedora 31

How To Test

Usual testing as when upgrading between major MariaDB versions.

Test that all other software runs well with MariaDB 10.5. Report any issues, so I can reach the different upstreams and check if they plan update their software to support MariaDB 10.5 and when.

User Experience

The users will have to upgrade their databases the same way as between major MariaDB versions.

If the users want to stick with MariaDB 10.4 for a little longer, the MariaDB 10.4 module is available for them in all stable Fedora releases as well as in Rawhide. If the users want to test the 10.5 series beforehand, the MariaDB 10.5 module is available.

Dependencies

Since the client library ('mariadb-connector-c') is not changing, dependent software should work fine.

Only a rare cases builds against the server part of MariaDB. (e.g. building a server plugin)

Packages that require the server (embedded) library "libmariadbd.so.19" are the only one that might need rebuild. Currently this is only a single package 'amarok', so I can cooperate with its maintainer if rebuild would be needed.

UPDATE 11/2020:
I checked the ABI compatiblity and the report can be found here:
https://mschorm.fedorapeople.org/abipkgdiff_mariadb-embedded_104-105
I tried to rebuild 'amarok' package in the COPR on top of the MariaDB 10.5 and it woked well:
https://copr.fedorainfracloud.org/coprs/mschorm/MariaDB_10.5_rebuild_test_area/builds/
I contacted the 'amarok' package mainatiner and we agreed on me submitting PR for 'amarok' package rebuild, once the MariaDB 10.5 land in Rawhide.

UPDATE 02/2021:
Package 'amarok' successfuly rebuilt on top of the MariaDB 10.5 during the F34 mass rebuild.

Contingency Plan

Contingency mechanism: In the worst case scenario, I would be forced to revert the change, bump MariaDB 10.4 package epoch and release F34 with MariaDB 10.4 instead.
Contingency deadline: Beta freeze.
Blocks release? N/A (not a System Wide Change)
Blocks product? N/A (not a System Wide Change)

Documentation

Upgrade startegy: https://mariadb.com/kb/en/library/upgrading-from-mariadb-104-to-mariadb-105/

Upgrading and incompatibilities: https://mariadb.com/kb/en/library/upgrading-from-mariadb-104-to-mariadb-105/#incompatible-changes-between-104-and-105

Release Notes

Release notes for each release: https://mariadb.com/kb/en/library/release-notes-mariadb-105-series/

Overall overview of the changes and improvements: https://mariadb.com/kb/en/library/changes-improvements-in-mariadb-105/

@@ Line 11: / Line 11: @@
 == Current status ==
+[[Category:ChangeAcceptedF34]]
 * Targeted release: [[Releases/34 | Fedora 34 ]]
 * Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
@@ Line 21: / Line 23: @@
 CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 -->
-* FESCo issue: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/2499 #2499]
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1902800 #1902800]
-* Release Notes tracking: <will be assigned by the Wrangler>
+* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/608 #608]
 == Detailed Description ==
@@ Line 40: / Line 42: @@
 == Scope ==
 * Proposal owners:
-**Prepare MariaDB 10.4 as a module for Rawhide and atleast one stable Fedora release (done)<br />so users which want to stay on the current release have the possibility.<br />This also serve as a failover mechanism in case of issues with the 10.5.
+**Prepare MariaDB 10.4 as a module for Rawhide and atleast one stable Fedora release ('''done''')<br />so users which want to stay on the current release have the possibility.<br />This also serve as a failover mechanism in case of issues with the 10.5.
-**Prepare MariaDB 10.5 as a module for Rawhide and atleast one stable Fedora release (done in Rawhide; the rest in BODHI)<br />so users can test the 10.5 in advance. (installing 10.5 module on already stable release)<br />This also serve as a upgrade path - users can install 10.5 module on Fedora release which have 10.4 in base; and then upgrade to 10.5 module on a Fedora release which will have 10.5 in base.
+**Prepare MariaDB 10.5 as a module for Rawhide and atleast one stable Fedora release ('''done''')<br />so users can test the 10.5 in advance. (installing 10.5 module on already stable release)<br />This also serve as a upgrade path - users can install 10.5 module on Fedora release which have 10.4 in base; and then upgrade to 10.5 module on a Fedora release which will have 10.5 in base.
-**Release MariaDB 10.5 to Rawhide (blocked; 10.5 modules needs testing first)
+**Release MariaDB 10.5 to Rawhide ('''done'''; 10.5 modules needs testing first, I got first positive responses)
-**Check software that requires or depends on 'mariadb' or 'galera' package for incompatibilities<br />This shouldn't be an issue in general, as vast majority of the software requires client library, provided by "mariadb-connector-c" package, which won't change.
+**Check software that requires or depends on 'mariadb' or 'galera' package for incompatibilities<br />This shouldn't be an issue in general, as vast majority of the software requires client library, provided by "mariadb-connector-c" package, which won't change. ('''done'''; 'amarok' package)
 **Gather user input on the changes between MariaDB 10.4 and 10.5
@@ Line 66: / Line 68: @@
 ==='''UPDATE (10/2020)'''===
-MariaDB 10.5 modules are now available for Fedora Rawhide and in BODHI for the stable releases
+MariaDB 10.5 modules are now available for Fedora Rawhide, Fedora 33, Fedora 32 and Fedora 31
 == How To Test ==
@@ Line 87: / Line 89: @@
 Only a rare cases builds against the server part of MariaDB. (e.g. building a server plugin)
+Packages that require the server (embedded) library "libmariadbd.so.19" are the only one that might need rebuild.
+Currently this is only a single package 'amarok', so I can cooperate with its maintainer if rebuild would be needed.
+'''UPDATE 11/2020:'''<br>
+I checked the ABI compatiblity and the report can be found here:<br>
+https://mschorm.fedorapeople.org/abipkgdiff_mariadb-embedded_104-105<br>
+I tried to rebuild 'amarok' package in the COPR on top of the MariaDB 10.5 and it woked well:<br>
+https://copr.fedorainfracloud.org/coprs/mschorm/MariaDB_10.5_rebuild_test_area/builds/<br>
+I contacted the 'amarok' package mainatiner and we agreed on me submitting PR for 'amarok' package rebuild, once the MariaDB 10.5 land in Rawhide.
+'''UPDATE 02/2021:'''<br>
+Package 'amarok' successfuly rebuilt on top of the MariaDB 10.5 during the F34 mass rebuild.
 == Contingency Plan ==
-Modules will provide the functional version of MariaDB 10.4, available to all users.
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: Fedora Modules for 10.4 available
+* Contingency mechanism: In the worst case scenario, I would be forced to revert the change, bump MariaDB 10.4 package epoch and release F34 with MariaDB 10.4 instead.
-* Contingency deadline: already in place
+* Contingency deadline: Beta freeze.
 * Blocks release? N/A (not a System Wide Change)
 * Blocks product? N/A (not a System Wide Change)
@@ Line 115: / Line 128: @@
 <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
 <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
-[[Category:ChangeReadyForWrangler]]
 <!-- Select proper category, default is Self Contained Change -->
 [[Category:SelfContainedChange]]
 <!-- [[Category:SystemWideChange]] -->

Search

Changes/MariaDB 10.5: Difference between revisions