Release support lifecycle

Release lifecycle and support

Our guide to software release management and support policies, including LTS and regular releases, end-of-support details, security updates, and user best practices.

Supported releases

VersionRelease dateEnd of support
113.x LTS14 Sep 202314 Sep 2024
3.x7 Mar 20237 Mar 2024
2.4.x29 Aug 202229 Mar 2023

Release types

  • LTS (Long-Term Support):
    • We create at least two LTS releases per year.
    • We support each LTS release for at least 12 months or N-2 LTS releases.
    • We end the support of an LTS release if at least two newer versions have been released and 12 months have passed.
    • An LTS release is explicitly marked as LTS. For example: v113 LTS.
  • Regular Releases:
    • We release non-LTS updates every two weeks.
    • Users must upgrade to the next release, as regular releases have no long-term support.
    • Regular releases are not marked as LTS. For example: v112.

End of support

  • For LTS Releases:
    • End of support occurs 12 months after the initial release date.
    • After this period, no further support or updates will be provided for the LTS version.
  • For Regular Releases:
    • These releases do not have a predefined end-of-support date.
    • Users are encouraged to stay up to date by upgrading to the latest release regularly.

Security updates

  • LTS Releases:
    • LTS releases receive regular security updates throughout their 12-month support period via patches.
    • These updates address security vulnerabilities and ensure the LTS version remains secure.
    • Major versions of internal components - such as database, tools, and frameworks - will not be changed during the LTS support period to maintain stability.
    • No new features are added to patches.
    • Patch updates on LTS also address bugs and defects.
  • Regular Releases:
    • Security updates are provided as part of regular releases.
    • Users are strongly advised to stay current with the latest regular release to receive the latest security patches.
    • Major versions of internal components may be updated in regular releases as they focus on introducing new features and enhancements.

Best practices

  • Users are encouraged to choose LTS releases when stability and long-term support are essential for their projects.
  • For those who require the latest features and can adapt to more frequent changes, regular releases are suitable. However, regular upgrades are necessary to stay secure and benefit from new functionality.
  • Security is a top priority, and all users are advised to apply security updates promptly to protect their systems and data.

Review and revision

This release support lifecycle document will be periodically reviewed and revised to reflect changes in the release and support processes.