Defining the API lifecycle in a modular, reusable, and machine readable way that can help others learn about what the API lifecycle could be, as as define their own evolving API lifecycle.
How do you calculate release velocity across all available versions? Without making assumptions on whether velocity is good or bad, but just determining to have fast an API is moving forward, changing, begin broken, patched, etc.
How do you calculate release velocity across all available versions? Without making assumptions on whether velocity is good or bad, but just determining to have fast an API is moving forward, changing, begin broken, patched, etc.