Settings and activity
1 result found
-
6 votes
Although this sounds reasonable in practice and many Linux distributions follow this, the projects we run at Aiven do not. So we are unable to build secured versions of open-source projects for long-term support. This would require an immense amount of engineering to maintain legacy versions of these 11 open-source projects. We also run Linux infrastructure, which is not part of the LTS model, so this would be yet another issue with the idea of LTS. If you'd like to discuss more, I am happy to speak with you.
An error occurred while saving the comment Chris Santiago supported this idea ·
For individual services like Kafka, LTS and/or longer supported release cycles are key when evaluating Aiven as a platform to other competitors. There is a high burden of a 1 year cadence and related testing need to verify that performance and functionality are not impacted. Many enterprise use cases are not looking to get on the latest release, which then cuts the potential full 1 year of support into the 6-9 month range.