Auto-update and 3.1.1

[GoogleCodeExporter]

It's time for 3.1.1 to be released with the few bugfixes we have. However the 
auto-update is still on 3.0.9 and will not work for a 3.0.9 - 3.1.0 update. So, 
what now?

3.0.9 - 3.1.0 blank update (or even replace index.php with directions to 
download 3.1.0) followed by 3.1.0 - 3.1.1 as normal.

x.x specific update.xml - i.e. every version has their own update.x.x.xml

update.xml that handles multiple upgrade paths. all versions would need 
updating to understand this. After that we could have 3.1.5 upgrade to 3.1.6 
and 3.2.2 upgrade to 3.2.3

I think the last approach is neatest but perhaps more effort than we really 
want. The quickest way is the first, with messages in the xml saying to 
download 3.1. Some people will ignore this and try to upgrade anyway, but that 
won't be fatal for their board as they can just download 3.1 after.

Any thoughts?

Original issue reported on code.google.com by kovellia on 4 Sep 2010 at 2:04

[GoogleCodeExporter]

I'd say go with the first method for now, and then later use the second option 
(with an update.xml for each major version rather than all versions (unless 
that's what you meant already)).

What was the issue with autoupdating to 3.1? Something to do with it backing up 
everything and likely timing out wasn't it?

Original comment by mastergamer0168@gmail.com on 4 Sep 2010 at 8:40

[GoogleCodeExporter]

Yes, that. Really a 3.0.8 issue, I think. There's also the lesser problem that 
the updater can't delete files. They're not killer, and could be worked around, 
but it's not as neat as it could be.

I may be being too perfectionist. ^^

Original comment by kovellia on 4 Sep 2010 at 9:33

[GoogleCodeExporter]

I had some problems with this that turned out to be because the 'old' files on 
the test board were newer than those in the update. Thus the updater skipped 
them. Secondly, the updater didn't allow the update level to be reset thus was 
stuck on 3.0.9. So I added the updater from trunk. There were 5 downloads of 
3.1.1 before I replaced it.

This was not the neatest release. ^^

I'll leave this issue open for now for any problems with the 3.1 auto-update.

Original comment by kovellia on 11 Sep 2010 at 3:20

[GoogleCodeExporter]

I have a suspicion that the file age problem may be related to the update 
problem in the first place, suggesting that it would have worked for most 
people anyway. C'est la vie.

Original comment by kovellia on 12 Sep 2010 at 3:43

[GoogleCodeExporter]

Original comment by kovellia on 26 Sep 2010 at 12:58

• Changed state: Done