Active development is happening on the master branch, and a new version is released from it
at the end of each quarter.
Stable releases of Envoy include:
- Extended maintenance window (any version released in the last 12 months).
- Security fixes backported from the
masterbranch (including those deemed not worthy of creating a CVE). - Stability fixes backported from the
masterbranch (anything that can result in a crash, including crashes triggered by a trusted control plane). - Bugfixes, deemed worthwhile by the maintainers of stable releases.
Hand-off to the maintainers of stable releases happens after Envoy maintainers release a new
version from the master branch by creating a vX.Y.0 tag and a corresponding release/vX.Y
branch, with merge permissions given to the release manager of stable releases, and CI configured
to execute tests on it.
Critical security fixes are owned by the Envoy security team, which provides fixes for the
master branch, and the latest release branch. Once those fixes are ready, the maintainers
of stable releases backport them to the remaining supported stable releases.
All other security and reliability fixes can be nominated for backporting to stable releases
by Envoy maintainers, Envoy security team, the change author, or members of the Envoy community
by adding the backport/review or backport/approved label (this can be done using repokitteh's
/backport command). Changes nominated by the change author and/or members of the Envoy community
are evaluated for backporting on a case-by-case basis, and require approval from either the release
manager of stable release, Envoy maintainers, or Envoy security team. Once approved, those fixes
are backported from the master branch to all supported stable branches by the maintainers of
stable releases. New stable versions from non-critical security fixes are released on a regular
schedule, initially aiming for the bi-weekly releases.
Release managers of stable releases are responsible for approving and merging backports, tagging stable releases and sending announcements about them. This role is rotating on a quarterly basis.
| Quarter | Release manager |
|---|---|
| 2020 Q1 | Piotr Sikora (PiotrSikora) |
In order to accommodate downstream projects, new Envoy releases are produced on a fixed release schedule (at the end of each quarter), with an acceptable delay of up to 2 weeks, with a hard deadline of 3 weeks.
| Version | Expected | Actual | Difference | End of Life |
|---|---|---|---|---|
| 1.12.0 | 2019/09/30 | 2019/10/31 | +31 days | 2020/10/31 |
| 1.13.0 | 2019/12/31 | 2020/01/20 | +20 days | 2021/01/20 |
| 1.14.0 | 2020/03/31 | 2020/04/08 | +8 days | 2021/04/08 |
| 1.15.0 | 2020/06/30 | |||
| 1.16.0 | 2020/09/30 | |||
| 1.17.0 | 2020/12/31 |