Quote:
Originally Posted by rob
The issue is a bug in the logic that detects that a new version is available that is required and necessitates a tightly coordinated update with the server. The bug in the CLIENT, and it will cause things to fail in obscure and confusing ways. That means that whenever we release the major update, anyone who has not yet updated to the interim release will encounter the same issue. There is nothing we can do to retroactively fix the version that users have running on their computers today, and that's the rub. The best we can do is fix the bug within the interim updates and get as many users as possible to install those updates before we release the major update.
So we are waiting until a meaningful percentage of users have updated to the interim releases so that they will not encounter this bug.
|
How are you collecting this metric? is it by installed base or by recent login? You do know that some significant percentage of any user base will have installed a software package and stopped using it right?