MariaDB Release Model
Current MariaDB Release Model (from 11.3 up)
- Releases happen four times a year.
- There is a new innovation release with new features every time. It is an RC release.
- Additionally, all maintained release series get a new patch version maintenance release, a release that was RC last time, becomes GA.
- There are no patch version releases of an innovation release after GA (except for emergency releases), instead users are supposed to upgrade to the next minor innovation release.
- Approximately every eighth innovation release (+-1, aligned around Debian release schedules) is a long-term support (LTS) release, maintained for five years after its first GA release
- An LTS release concludes a major release series, the next innovation release will have a new major version number
- Between two innovation releases there is a preview, it is feature-complete, but has alpha maturity, its purpose is to showcase new upcoming features. Every feature that will be in a release must have been in a preview at some point
- The opposite is not true, the feature from a preview will not necessarily be in the upcoming RC innovation release — this depends on whether the feature itself can be considered RC. If it isn't stable enough, it'll stay on internal testing and bugfixing until it is ready.
The release schedule looks about the same every year:
- Every third month there's a new minor innovation release and new patch versions maintenance releases:
- early February, early May, early August, early November
- Previews happen between innovation releases:
- mid-March, mid-June, mid-September, mid-December
- New major release every second year
- GA is early February on odd years (so, RC in November, preview in mid-September)
Historical MariaDB Release Models
from 10.7 to 11.2
Almost the same as above, except that
- An innovation release is maintained for one year after its first GA release (see, for example, timeline of 10.10 releases)
from 10.2 to 10.6
- There is a new release series every year
- It's maintained for five years after the first GA release
- A release is going through conventional alpha, beta, RC maturity phases until reaching GA
- The first GA is planned to happen in May
from 10.0 to 10.1
- It is a feature based model
- A new release series is planned to have a specific set of features
- It is released when they are ready
- Conventional alpha/beta/RC/GA maturity phases.
- No fixed or predictable schedule
- 10.0 took 2.75 years (first commit was in August 2011, GA in May 2014)
- 10.1 took 1.83 years (first commit was in December 2013, GA in October 2015)
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.