Percona Release Lifecycle Milestones Overview
The Percona development process adheres the following release lifecycle milestones for major new software releases.
Alpha releases
Usually unannounced, an alpha release is distributed internally, or only to a select external audience to be tested with non-production workloads only.Platform Support: | All or a subset of currently supported and/or targeted platforms. |
---|---|
Features | New features are being added, but not committed to GA. Features may be removed. While some features are complete, many are still in development or being added. |
Documentation | Draft only for completed features — not viewable, with release notes internal only. |
Quality | Users can start trying out Alpha versions, but should not expect feature stability. |
Support | Internal-only support. |
Beta Releases
Usually public, announced via our blog . To be used with non-production workloads only.Platform Support | All targeted platforms. |
---|---|
Features | New features in this release will be included in GA. Most features are complete, some new minimal features are still being added. |
Documentation | Draft only for completed features and install/config updates, as needed — not viewable. Release notes include a cumulative list of new features, improvements, and bug fixes since the previous major version. |
Quality | Features are mostly stable, but data loss can occur; the focus is on usability and scalability. |
Support | Community support provided via Percona Community Forum; bugs should be submitted via Jira . |
Release candidates
As a public release, release candidates are announced and distributed externally, however are still intended to be tested with non-production workloads only.Platform Support | All targeted platforms. |
---|---|
Features | Features are complete with tech preview* features identified; only bug fixes are accepted at this stage. |
Documentation | The draft is near-final and publicly viewable, with a cumulative list of new features, improvements, and bug fixes since the previous major version. Does not include bugs fixed since a previous Beta or RC release unless reported by a user. |
Quality | Features are stable; the focus is on final testing and critical issues being resolved. |
Support | Community support provided via Percona Community Forum; bugs should be submitted via Jira . |
General Availability (GA)
The final stage, a General Availability (GA) release, is announced and distributed externally and ready for production workloads. Distribution is via full packages (.rpm, .ovm, docker, .deb, etc), repositories, and marketplaces.Platform Support | All targeted platforms. |
---|---|
Features | Features are complete and will not be removed in future versions of the same major release; may include tech preview* features. |
Documentation | Complete, integrated, and viewable, with a cumulative list of new features, improvements, and bug fixes since the previous major version. Does not include bugs fixed since a previous Beta or RC release unless reported by a user. |
Quality | Quality passed up to GA exit criteria. |
Support | Full SLA-based support, with the availability of managed services and consulting. |