View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0034909 | mantisbt | administration | public | 2024-10-27 06:06 | 2024-10-27 12:44 |
Reporter | dregad | Assigned To | dregad | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Target Version | 2.28.0 | ||||
Summary | 0034909: Admin checks: unsupported version checks using endoflife.date | ||||
Description | Our admin checks currently perform end-of-life and vendor-support checks for MySQL and PostgreSQL databases only. These are manually maintained, forcing us to periodically update the reference table as new versions are released, and rely on custom logic to determine whether a version is supported or not, based on its release date and information from the vendor's web sites. https://endoflife.date provides community-maintained information about release lifecycle for various software components, which we should leverage to simplify the admin checks' code and relieve us from the hassle of having to update the versions reference tables. As an added benefit, it would also allow checking for SQL Server and Oracle database support using the same code, as well as PHP. | ||||
Tags | No tags attached. | ||||
related to | 0028525 | closed | atrol | Using MySQL 8.0 gives warning in admin checks |
related to | 0028528 | closed | dregad | Outdated PostgreSQL version information in Admin Checks |
related to | 0034887 | resolved | dregad | MySQL version 9.0 and 9.1 are not defined in Admin Checks |
related to | 0034886 | assigned | dregad | Admin checks: support MariaDB version checking |
related to | 0034916 | resolved | dregad | PostgreSQL versions 16 and 17 are not defined in Admin Checks |