LTS editions
As a product owner of Aiven services
I want to be able to select Long term support versions of the Aiven products
so that I can have the upgrade cycles match those of my other products without having to request exceptions when End of life warnings start appearing
In addition, I'd like to be able to made aware of any maintainence done to my clusters if they are in anyway destructive.
Ben Gamble
shared this idea
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.
-
Chris Santiago
commented
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.