Topic: Incorrect detection and setting of latest version
I've been following some programs that seem to be getting the latest version reset incorrectly.
One such program is xplorer2.
The official latest version is: 1.7.2.6 (7.Jun.09)
SI latest version keeps getting reset to 1.65 (possibly when the developer released 1.6.5.x)
I post an incorrect version notice to have it corrected to 1.7.2.6 and it seems fine for a day, and then perhaps another user runs the client with 1.65 and the 1.7.2.6 "latest version" gets over written.
eg. (from notifications)
14-Aug-2009 - v 1.71
6-Sep-2009 - v 1.65
10-Sep-2009 - v 1.71
12-Sep-2009 - v 1.65
Note that NONE of these are the correct - 1.7.2.6 (which I have submitted reports for over the past weeks).
I've got to ask - what the heck is going on back there?
It's not only xplorer2. I've seen equally fictitious results for K-Meleon - I've been notified 2 or 3 times recently about the release of version 1.10. I've no idea where this imaginary release fits into the release history - http://kmeleonbrowser.org/download.php
And there are others I have sent reports in for over the past weeks and the SI entries remain at this moment, incorrect.
If a user cannot see valid version information or even consistent version information from day to day - how are we supposed to trust the application at all?