Project commitments for the maturity stages of MariaDB Releases
The MariaDB development release policy has the following project commitments for the maturity stages:
New features are being added. Some old features may be removed. Users can start trying Alpha versions out, but should not expect feature stability yet. Still, should show no regressions and should have no open level bugs for this release.
Features can not be removed anymore. Users can start building applications using MariaDB Beta releases. Any application that works with MariaDB Beta release will continue to work with a RC and GA release. The syntax that was valid in Beta will stay valid, tables created in Beta will stay readable, Beta clients will be able to connect to GA servers, and so on.
The server is feature complete. No new features, no changes in default settings are possible. From this point only bug fixes are accepted into the server.
We believe the code is ready for general usage (based on bug inflow).
Plugins generally follow the same rules, but they have . That is, a plugin is declared Gamma when it becomes feature complete. This happens independently from the server being Alpha, Beta, RC, or GA.
See our page for information of how and when emergency security releases are done.
This page is licensed: CC BY-SA / Gnu FDL