JEP 14 proposes the 'Tip & Tail' release model for Java libraries, inspired by how OpenJDK itself has operated since version 9. The model splits a project into a 'tip' (main development branch with new features) and one or more 'tails' (maintenance branches receiving only critical bug and security fixes). This separation lets library maintainers innovate freely on the tip using modern JDK features, while guaranteeing stable, low-churn updates for users who depend on tail releases. Tails must only depend on other tails, preventing butterfly-effect dependency updates. The model also provides shared vocabulary for discussing dependency challenges and is positioned as a conversation starter for the broader Java ecosystem.

9m read timeFrom nipafx.dev
Post cover image
Table of contents
▚ Defining Tip & Tail▚ Benefits for Users & Maintainers▚ Managing Tip & Tail Dependencies▚ Nomenclature & Lightning Round

Sort: