[MDBF-237] downloads - Old Stable is confusing - remove Created: 2021-03-08  Updated: 2023-08-28  Resolved: 2023-08-28

Status: Closed
Project: MariaDB Foundation Development
Component/s: Downloads
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Daniel Black Assignee: Vicențiu Ciorbaru
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Old Stable has been used for releases for a while. We don't however give it a formal meaning.

We are using this for 10.2+ -> 10.5 versions currently.

A user could easily be confused by this an arrive at any of the following incorrect conclusions:

  • There are no more updates on these version.
  • There are only security updates on these versions (Like Debian Old Stable).
  • The old stable versions are less supported by MariaDB
  • The old stable versions are more stable than new stable (probably actually true, but not intentionally so).

Given this ambiguity can we remove the use of the term.

 Comments   
Comment by Vicențiu Ciorbaru [ 2021-11-29 ]

andreia.hendea I can not think of any particular reason why "Old Stable" should be kept. Have a look at any of the code paths using that (namely repo-config tool and drop-down selection for downloading individual files). If nothing depends on it, remove the "Old Stable" notion and mark all those releases as just "Stable".

Comment by Ian Gilfillan [ 2022-05-23 ]

This is used ambiguously currently. 10.8 and 10.7 are marked as "Stable". 10.6 and below are marked as "Old Stable". If used at all, 10.7 and 10.6 should be switched, as 10.6 is the current LTS, while 10.7 is a previous short-term release.

Comment by Vicențiu Ciorbaru [ 2022-05-23 ]

I suggest we should have releases be labeled as:

GA - Short Term Support
GA - Long Term Support
RC
Gamma
Beta
Alpha
EoL

greenman, danblack Opinions? This would be in line with what we actually have.

Comment by Ian Gilfillan [ 2022-05-23 ]

Can we use the full names? We're all familiar with RC, GA etc, but is everyone? Otherwise happy in principle.

Comment by Daniel Black [ 2022-05-23 ]

On the user interface it looks ok.

On a REST API its putting too many values in a single field. On a branch status there are three main concepts covered here:

  • Development status, InDevelopment, Maintenance, EoL
  • Code maturity status, Alpha...GA
  • Support status, partially derived from Developments status (or vis versa) should include EndOfLiveDate, and a LTS/ShortTermSupport flag would be useful too.

On the REST API for a specific release version 10.7.4 (MDBF-236) there should be only the code maturity status.

FYI https://endoflife.date/mariadb, and a bunch of other EOL information exposed.

Comment by Ian Gilfillan [ 2022-08-17 ]

Appears in https://downloads.mariadb.org/rest-api/mariadb/

Comment by Ian Gilfillan [ 2022-08-17 ]

cvicentiu do you agree with danblack? We need to get clarity on what text to use.

Generated at Thu Feb 08 03:36:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.