What does "stable" really mean in relation to code? [closed]

Question

I often see or hear people describe something as "stable" in relation to code.

Am I right in thinking that a "stable" class library is one in which the functions have been well tested, used in the real world and not been found to contain any bugs? Or at least any purpose critical bugs.

How, then, does this relate to large pieces of software like operating systems? I often see a download described as "stable", which is usually a few versions behind the latest releases. Exactly when does a piece of software become stable? Are there any criteria for determining this?

Answer 1

Its not being changed a lot. Usually that means its good, working and has no bugs.

A "stable" release in terms of libraries is typically a "recommended" release where a more "bleeding-edge" release is also available. In such a scenario it is wise to use the stable release for production code.

Exactly when does a piece of software become stable? Are there any criteria for determining this?

This is a very subjective piece of criteria. Typically its a result of the release having undergone rigourous QA and/or having been released without any serious issues being reported. However the usage of the term depends on the team's measurement so one man's "stable" might not be anothers.