For the general availability of its 3.0 major release, Oracle’s Micronaut team collaborated to build recipes to perform most of the upgrade automatically. This is the first major sign of a paradigm shift we want to see in who is responsible for repairing code when breaking API changes are made. We’d like to see the responsibility shift to the framework author that introduces the change.
By taking on this additional responsibility, the promise for framework authors is a shorter major release cadence, and the ability to make more significant changes, without the traditional downside of impact on their communities.
