Developers told to hurry up and get features stable as support for other features extends to help slow upgraders
The Kubernetes project has decided the time has come to stop existing in a state of permanent beta. The decision, included in the Changelog for version 1.19 of the container-wrangling code and explained in a blog post, reflects the fact that Kubernetes offers plenty of REST APIs and they can evolve… or not. The project’s new rules mean that when a new feature’s API reaches beta, a nine-month countdown commences. Within that timeframe, the beta must either reach general availability (which deprecates the beta) or start anew (which deprecates the previous beta). “The motivation here seems pretty clear: get features stable,” wrote Kubernetes contributor Tim Bannister of The Scale Factory.
