To answer your question:
> Why can't 1.5 just be 15.

The real answer to your question can best be summed up in the phrase, "the
best laid plans of mice and men . . ."  In other words, sound software
development is a blend of optimistic planning and the cold realities of
Murphy's laws.  A 1.5 "release" is enumerated as such because the "generic"
(1.0) is a planned distribution of software architected with advertised
capabilities.  A "release" (5) are subsequent distributions of the major
"generic" distribution to correct subtle (and sometimes not so subtle)
design flaws.  And a "load" number (1.5.68) is typically an internal (to the
software development organization) to correct implementation and coding
flaws (bugs).

It does surprise me that some software vendors do include the entire version
number in the product identity, frankly it really is not a customer's
concern if it takes 1 load or 812 loads to get a product in shape for
release.  But I will suggest that relatively uninspired version control is
in effect where such high numbers are in the load portion of the version
number.

To summarize, using Version X.Z.Y:

Generic number (X) occupies the left most position indicating the
incarnation of the product architecture -- in this case it would most likely
be the first incarnation.

Release number (Y) occupies the middle position and typically corresponds to
design improvements (performance, user interface, etc).

Load number (Z) occupies the right-most position and is typically an
increment of compilations to achieve a distributable product -- tantamount
to "acceptable" incidences of bugs.


------------
Bill Gallik
E-Mail: [log in to unmask]


VICUG-L is the Visually Impaired Computer User Group List.
To join or leave the list, send a message to
[log in to unmask]  In the body of the message, simply type
"subscribe vicug-l" or "unsubscribe vicug-l" without the quotations.
 VICUG-L is archived on the World Wide Web at
http://maelstrom.stjohns.edu/archives/vicug-l.html