Deprecate support for MariaDB 10.2.6 and older #5102
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an addendum to #5097.
The DBAL uses a separate platform class for MariaDB 10.2.7 and newer:
dbal/src/Driver/AbstractMySQLDriver.php
Lines 37 to 38 in dfdb5fb
Although the 10.2 release series will be supported until May 2022, MariaDB 10.2.6 was released in May 2017, so those who still use one of the 10.2 releases likely use version 10.2.7 or newer.
If we deprecate only 10.1 and test the remaining supported versions on CI starting with the
10.2
docker image tag (which currently is an alias for10.2.41
), the support for the releases 10.2.0 through 10.2.6 will be effectively untested.Keeping a separate set of build jobs for testing a 4-years old release seems unjustified. By the time when DBAL 4.0 is released, we will likely drop the support for the entire 10.2 series anyways.