Guide to Software Revisions

[Talisman]

1.0: 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.

1.1: We fixed all the killer bugs ...

1.2: Uh, we introduced a few new bugs fixing the killer bugs and so we had to fix them, too.

2.0: We did the product we really wanted to do to begin with. Mind you, its really not what the customer needs yet, but were working on it.

2.1: 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 dont think we introduced any new bugs while we were fixing these bugs.

2.2: Uh, sorry, one slipped through. One lousy typo error and you wont believe how much trouble it caused!

2.3: Some jerk found a deep-seated bug thats been there since 1.0 and wouldnt stop nagging until we fixed it!!

3.0: Hey, we finally think weve got it right! Most of the customers are really happy with this.

3.1: Of course, we did break a few little things.

4.0: More features. Its doubled in size now, by the way, and its written in a different language now and you'll need a bigger server ...

:lick: