New informational JEP: 14: The Tip & Tail Model of Library Development

[Karsten Silz]

The JEP solves the problem of new features and improvements breaking the application for users seeking stability, at the cost of maintaining multiple trains and some backporting. My hypothesis is that "new features and improvements breaking the application" is not an issue for some "One size fits all" Java libraries today, probably smaller ones.

How can I (or somebody else) prove or disprove my hypothesis? 

Assuming my hypothesis is true: Should the libraries without this problem still switch to Tip & Tail?


Regards,
Karsten Silz


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jdk-dev/attachments/20241112/df8968df/attachment.htm>