Software Version Explanations

Once you start playing with software you quickly become aware
that each software package has a revision code attached to it. It is
obvious that this revision code gives the sequence of changes to the
product, but in reality theres substantially more information
available through the rev-code than that. This article provides a
guide for interpreting the meaning of the revision codes and what they
actually signify.

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. Were praying that
youll find it more functional than, say, a computer virus and that
its operation has some resemblance to that specified in the marketing

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
youll need to get more memory and a faster processor …

4.1: Just one or two bugs this time… Honest!

5.0: We really need to go on to a new product, but we have an
installed base out there to protect. Were cutting the staffing
after this.

6.0: We had to fix a few things we broke in 5.0. Not very many,
but its been so long since we looked at this thing we might as
well call it a major upgrade. Oh, yeah, we added a few flashy
cosmetic features so we could justify the major upgrade number.

6.1: Since Im leaving the company and Im the last guy left in
the lab who works on the product, I wanted to make sure that all
the changes Ive made are incorporated before I go. I added some
cute demos, too, since I was getting pretty bored back here in my dark
little corner (I kept complaining about the lighting but they wouldnt
do anything). Theyre talking about obsolescence planning but theyll
try to keep selling it for as long as theres a buck or two to be

Most viewed Jokes (20)