Release Management and Support Guidelines
Our guide to software release management and support policies, including LTS and regular releases, end-of-support details, security updates, and user best practices.
- LTS (Long-Term Support):
- We create at least two LTS releases per year.
- Each LTS release is supported for at least 12 months or N-2 LTS releases. An LTS release is dismissed if at least two newer versions have been released and 12 months have passed.
- An LTS release is explicitly marked as LTS. E.g. v113 LTS.
- Regular Releases:
- We release updates every two weeks, but these are not LTS.
- Users must upgrade to the next release, as regular releases have no long-term support.
- Regular releases are not marked as LTS. E.g. v112.
- 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.
- 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.
- 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 should be a top priority, and all users are advised to apply security updates promptly to protect their systems and data.
This release support lifecycle document will be periodically reviewed and revised to reflect changes in the release and support processes.