Re: Re-Release Problems
Maybe this is not addressing the real problem, but how about putting a sort of "expiry" date in some versions of your program?
IF you have an Auto-Update feature, you can keep a little file on your server. As soon as you notice the previous version is bugged etc, you set some options in it, and so people using the auto-update will be told that they need to get a new version.
OFC this only works if they check the update frequently enough etc (can be annoying as well bla bla).
Could be too late of course, as the current version is out, and it might NOT have this "check version" feature thingy...
To your other issue: Maybe just increase your new version number by a large step, so people will notice the drastic changes (bugfixes) you've made.
Also, for future versions: Don't be too optimistic with version numbers like "1.0". I know, we currently life in a time where 1.0 usually means bullshit, and you can only trust lots of programs if they are patched a couple of times.
But, there are also really nice & stable betas, like 0.85 etc, which are in use all the time.
So, just always call a version 0.99 before you release it first.....
This is too late again obviously, as you're facing a different problem.
I'm interested, what's your project about?
__________________
[ ğ] Entropy increases! :-/
|