Would it be possible to include the version number in the core file name of every release bundle?
The current model is: Specify_windows.exe
Suggested model: Specify_windows_6_1_0.exe
I understand that updates are available within the software, but my goals are ready access to older versions, and confidence that an independent localhost test user can confidently download the "right" version that matches the one used in an institution. Thanks!
Or can anyone suggest a better, more developer-standards-compliant model?
Second that motion
Due to some wonkiness with a previous update release, we began maintaining an archive of downloaded Specify_windows.exe's each of which is differentiated by folder name.
To avoid future calamities, we manually backup our database prior to any Specify 6 update. If there are issues with the update release (as there have been a couple of times now) we can re-install the old version and restore the database. But without version control in the file name, this becomes tricky.
Previous Releases
We have a fairly automatic build process and it is easier for us to not include the release number in the name. I'll admit that it would be very handy. I suggest renaming the downloaded file for your own purposes.
I have made available several previous releases at the bottom of the downloads page. We will continue to keep this updated with each release.
http://specifysoftware.org/content/download