Stable - Api. Does software still work from three years ago?

I saw yet another 0.x piece of rapidly changing python code calling itself stable today.

If your code meets any of these criteria your code is not stable.
  • Is not even six months old, with a 0.x version number with massive changes planned.
  • Your code is still old and changing rapidly with massive changes planned.
  • Your api is changing causing breakages.
A good test to see if your library/framework is stable is to take some old program and see if it runs correctly, as it used to. If it doesn't, then your library/framework is not stable.


ah... words that have different meanings.

Comments

Florian said…
In theory unit-tests, regression-tests, UI-tests and smoke-tests should show you reliably when you start breaking backwards compatibility.

Popular posts from this blog

Draft 3 of, ^Let's write a unit test!^

Is PostgreSQL good enough?

post modern C tooling - draft 6