MariaDB Maintenance Policy
The MariaDB project is a community project governed by the MariaDB Foundation. The MariaDB Foundation has an Engineering Steering Committee (ESC), which is an elected body and represents the technical leadership. It’s ultimately up to the ESC to accept commits against any version of MariaDB and also correspondingly decide which versions of MariaDB should be built and packaged.
The MariaDB project is as active as the community around it and the MariaDB Foundation members actively working on and enhancing MariaDB. Therefore, from the MariaDB project perspective, the aspiration is for each major version of MariaDB to be maintained for five years after its initial stable (GA) version. The guideline for supporting this policy is that bug reports not accepted by a member within 1 month on any major release over 5 years old will be marked "unmaintained" and closed. If bug reports are accepted within the 1 month timeframe, builds will only be packaged if the ESC expressly requests this.
With this guideline in mind and the aspiration of having each major release maintained for five years after the first stable (GA) release all current versions of MariaDB — 5.1, 5.2, 5.3, 5.5 and 10.0 — are currently "maintained". The following schedule shows the dates when this will change:
| Major Version | Stable (GA) Date | Five year boundary date |
|---|---|---|
| 5.1 | 1 Feb 2010 | 1 Feb 2015 |
| 5.2 | 10 Nov 2010 | 10 Nov 2015 |
| 5.3 | 29 Feb 2012 | 1 Mar 2017 |
| 5.5 | 11 Apr 2012 | 11 Apr 2017 |
| 10.0 | 31 Mar 2014 | 31 Mar 2019 |
| 10.1 | Not Stable | 5 years after stable (GA) release date |
Members of the MariaDB Foundation can of course offer services to their customers that cover the versions even longer and provide SLA commitments. MariaDB Foundation does not provide support; if you need it you should contact one of our members.
