Quote:
Originally posted by mwarden
I'm going to have to disagree with the idea of forced upgrades.
If you want to implement some nagging system, that's fine. There's already the "there's a new version of Limewire" message, that has previously included information about why it's absolutely necessary to upgrade. But, in the end, it was still my decision to install the new version.
I don't see the reason for taking the step from strong encouragement to force. It's enough to make some people suspicious of what all is included in the upgrade and possibly switch clients (or, edit the source to bypass the check). |
Why do you think that I want a forced upgrade?
I was speaking exactly about the condition that makes the "upgrade available" alert to appear. What would be forced is the display of this information box. By "expiring" I mean really the condition that allows a servent to run without this forced message at startup. Users can still dismiss and choose to update later...
But if they ignore it and restart the servent, they will see again this dialog (once).
This is an important feature notably for beta versions and CVS-compiled versions (with its own signed "update.ver" file), so that preliminary code will not harm the network for too long after a major bug is discovered.