Relationship Graph

Relationship Graph
related to related to child of child of duplicate of duplicate of

View Issue Details

IDProjectCategoryView StatusLast Update
0034480mantisbtdb mysqlpublic2024-10-22 18:04
ReporterTak-MK Assigned Todregad  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version2.26.2 
Target Version2.26.3Fixed in Version2.26.3 
Summary0034480: Using MySQL 8.4 gives warning in admin checks
Description

Running admin/check/index.php gives warning when using MySQL 8.4

MySQL Lifecycle and Release Support data availability
Release information for MySQL 8.4 series is not available, unable to perform the lifecycle checks.
Additional Information

Related to https://mantisbt.org/bugs/view.php?id=28525

TagsNo tags attached.

Relationships

related to 0028525 closedatrol Using MySQL 8.0 gives warning in admin checks 
related to 0034887 closeddregad MySQL version 9.0 and 9.1 are not defined in Admin Checks 

Activities

dregad

dregad

2024-06-26 11:05

developer   ~0069006

MySQL changed their lifecycle model with so-called Innovation and LTS releases; this will require changes to the Admin Check codes to take the new release types into consideration.

diedie2

diedie2

2024-06-27 01:53

reporter   ~0069008

Fact is you get a warning when using an "older" version

image.png (25,885 bytes)   
image.png (25,885 bytes)   
dregad

dregad

2024-06-30 09:03

developer   ~0069015

PR https://github.com/mantisbt/mantisbt/pull/2012

Related Changesets

MantisBT: master-2.26 42476765

2024-06-30 07:21

dregad


Details Diff
Add newer MySQL releases to Admin Checks list

Fixes 0034480
Affected Issues
0034480
mod - admin/check/check_database_inc.php Diff File

MantisBT: master-2.26 141fec8a

2024-06-30 07:32

dregad


Details Diff
Adapt MySQL Admin Checks to new release model

With Oracle's introduction of Long Term Support (LTS) and Innovation
releases in 2023 [1], the logic implemented in check_database_inc.php
for the old General Availability (GA) model is no longer applicable.

This commit adapts the logic as follows:
- releases <= 8.0 use the former model with a GA version marking
start of official support, 5 years active + 3 years extended)
after which the release is considered end-of-life
- LTS releases basically follow the same model, but the GA version
is always the .0 (8.4.0 is the first LTS release)
- Innovation releases support ends when the next version is released,
or 3 months after go-live if the next release is not defined

Fixes 0034480

[1]: https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions
Affected Issues
0034480
mod - admin/check/check_database_inc.php Diff File

MantisBT: master-2.26 0199cd42

2024-06-30 07:33

dregad


Details Diff
Convenience link to report missing MySQL release

When using a MySQL release not defined in the $t_versions array, the
database admin checks prints an error message to inform user that life
cycle checks can't be performed.

This commit improves the message with a link to the MantisBT bugtracker,
opening a pre-filled bug report.

Fixes 0034480
Affected Issues
0034480
mod - admin/check/check_database_inc.php Diff File