[IronPython] please document file version numbers

Dino Viehland dinov at microsoft.com
Tue Feb 17 21:28:25 CET 2009


Good suggestion - I've added this information to the release notes page for both 2.0 and 2.0.1.  Updating the read me (in particular in the MSI) is more difficult due to needing to re-sign the MSI.  But we should do that for future dot releases.

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Jonathan March
Sent: Tuesday, February 17, 2009 12:21 PM
To: users at lists.ironpython.com
Subject: [IronPython] please document file version numbers

> file version changes with every patch so you can determine exactly what version you have

I can find no documentation of the relationship between release version numbers (e.g. 2.0.1) and file versions (i.e. 2.0.20209.0). I would suggest that the file version number be listed in the following two locations:
1. The release download page
2. The read-me file for the release.

===

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Dino Viehland
Sent: Friday, February 13, 2009 3:32 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Announcing IronPython 2.0.1

... Minor non-breaking releases are in-place upgrades ... But its file version changes with every patch so you can determine exactly what version you have. ... for minor versions not reving the assembly version is also a way of life.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20090217/0e83ac06/attachment.html>


More information about the Ironpython-users mailing list