Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added 4.17.1.0 release timeline

...

When a CVE is identified, the security team requires a private, expedited release process to address the issue.  Users also need a release that is constrained to fixing only the CVE to minimize upgrade risk and downtime.  Therefore, when a security release is required, the security team will review the proposed patch privately with a minimum of two (2) LGTMs required per our release principles.  The patch will be forward merged to every impacted regular and LTS release currently supported – incrementing the security patch number.  The security team will then create a release candidate for each security release and vote on each release candidate according to the community's bylaws. Security issues should be reported to security@apache.org  

LTS Release Calendar

ReleaseTypeRelease DateEOL
4.9.0Regular25 July 2016
4.9.1.0

LTS

15 December 20161 July 2018
4.9.2.0LTS6 January 20171 July 2018
4.9.3.0LTS11 September 20171 July 2018
4.11.0.0LTS12 February 20181 July 2019
4.11.1.0LTS2 July 2018
4.11.2.0LTS26  November 2018
4.11.3.0LTS13 Jul 2019
4.12.0.0Regular 4 April 2019 
4.13.0.0LTS24 September 20191 May 2021
4.13.1.0LTS2 May 20201 May 2021
4.14.0.0LTS26 May 20201 Jan 2022
4.14.1.0LTS3 March 20201 Jan 2022
4.15.0.0LTS19 Jan 20211 July 2022
4.15.1.0LTS
1 July 2022
4.15.2.0LTS
1 July 2022
4.16.0.0LTS15 November 20211 June 2023
4.16.1.0LTS
1 June 2023
4.17.0.0LTS7 June 20221 Jan 2024
4.17.1.0LTS
1 Jan 2024

Notes:

  • These dates assume that no blocker or critical defects are identified that require an earlier release
  • Release dates are based on the git tag or source tarball date
  • LTS releases starting with the first major release will be supported for a minimum of 6 months after next LTS release or a total period of 18 months, whichever is greater

...