A Guide to Software Revisions
Also known as "one point uh-oh", or "barely out of beta". We had to
release because the lab guys had reached a point of exhaustion and
the marketing guys were in a cold sweat of terror.
We fixed all the killer bugs ...
Uh, we introduced a few new bugs fixing the killer bugs and so we
had to fix them, too.
We did the product we really wanted to do to begin with. Mind you,
it's really not what the customer needs yet, but we're working on it.
Well, not surprisingly, we broke some things in making major changes
so we had to fix them. But we did a really good job of testing this
time, so we don't think we introduced any new bugs while we were
fixing these bugs.
Uh, sorry, one slipped through. One lousy typo error and you won't
believe how much trouble it caused!
Some jerk found a deep-seated bug that's been there since 1.0 and
wouldn't stop nagging until we fixed it!!
Hey, we finally think we've got it right! Most of the customers are
really happy with this.
Of course, we did break a few little things.
More features. It's doubled in size now, by the way, and you'll need
to get more memory and a faster processor ...