|
The Truth About Version Numbers
How should a software revision level be interpreted? Here's a quick guide for anyone short of a clue:
0.1 - We've got a really great way to do things.
0.9 - We think it works, but we won't bet our lives on it.
1.0 - Management is on the case; seems like a low risk.
1.01 - Okay, we knew about that; all known bugs are fixed.
1.02 - We've fixed bugs you wouldn't see in 27,000 years, i.e. more than three times the age of the universe.
1.03 - Fixes bugs in the bug fixes.
1.04 - All right, this really does fix all known bugs.
1.05 - Fixes the bugs introduced in revision 1.04.
1.1 - A new crew has been hired to write the documentation.
1.2 - Somebody has actually changed a functional feature.
2.0 - Another new crew has been hired to write software. The old crew is blamed for all previous bugs.
2.01 - The new crew has sent out their resumes to placement agencies.
Go back ten squares and return to version 0.1
|
