Sustainable open source is a vexing problem, and I hope Lightbend find success in the new model for Akka and continues the proud tradition of innovation.
I propose that a release-2.6 branch is maintained under the Apache 2.0 License for critical bugfixes and security patches only until September 2023. The Lightbend Support Terminology states:
Lightbend commits to providing 1 year advance notice before ending support for any Supported component, so an EOL announcement will include the date on which a product is EOL. A product remains Supported until the EOL date. Once the EOL date passes, Lightbend will no longer support the product.
The definition of supported (emphasis mine):
Applies to any product for which Lightbend will provide fixes and patches to subscribers on request.
The policy justifiably promises nothing to non-subscribers, but I believe a traditional Akka EOL cycle is still advantageous to Lightbend.
- Enterprise procurement is a grueling process. As a staff engineer, I can’t produce a check today, but I have to answer security questions every day. Today I could only shrug.
- Some will realize the value in the product and subscribe. Others will have time to make a responsible migration. Either way, predictable EOL cycles preserve Lightbend’s brand as a dependable business partner in future consideration.
- There is still incentive to subscribe ASAP and enjoy the innovations that 2.7 will bring.
- The burden is hopefully low. There were only five releases of 2.5.x in the year after 2.6.0, and the bar might be higher for the wind down of 2.6.x.
I hope the patch policy is reconsidered as Akka transitions to its new business model. This change would makes the pivot just as definite, but much less jarring.
Thanks for your consideration.
1 post - 1 participant