12 years of Python and only at v2.2

[Bradley D. Larson]

When you are revenue based (both sales and/or support) you must continue to produce
a new version or upgrade regularly to produce revenue and keep your loyal support
paying captives happy. This usually generates at least one "upgrade" (minor
version) every 6 months and a major version upgrade every 12-18 months. Without
this
the revenue stream would come to a screeching halt. On this scedule you will
naturally move up 6 to 7 major versions in a ten year period.

Where revenue is not the driving factor updates are usually better thought out,
better tested major version numbering is used for just that; major version
changes.  I work in IS and see a lot of "major version" changes that do not do
anything more than a few cosmetics and some other minor changes yet the version
jumps a who version.

John Goerzen wrote:

> I think the notion that any insight into the code itself can be gained by a
> version number alone is generally fallacious, save perhaps for the ability
> to determine how many marketroids are involved :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blarson.vcf
Type: text/x-vcard
Size: 400 bytes
Desc: Card for Bradley D. Larson
URL: <http://mail.python.org/pipermail/python-list/attachments/20021204/abc3ab50/attachment.vcf>