Include the build date in version information #533
Description
Describe the suggested improvement
A user may be using an outdated version of the tool and run into a bug that has already been fixed. The version update is supposed to catch this, but it's possible that the environment the tool is run in may not have outbound Internet access.
Saying that the version is X.Y.Z but also that it was built on (DATE) might give a better hint that it should be updated.
Additionally, if an uncaught error occurs, but we were not able to perform the update check, the tool could say something like "This version of the tool is X months old. It's possible that this bug was fixed in a later version." Then it could link to the documentation for updating.
Additional Context
Our release history is currently:
- 0 so far in July (as of July 24)
- 3 releases in June
- 2 in May
- 0 in April
- 4 in March
Before that the initial task force was regularly making updates to the tool, so the data is less useful. But it appears infrequent (so far) that we have gone more than 2 months without some sort of release.