Beginning with the next releases we change our versioning scheme a bit to support test (beta) builds inside our release cycles. Because OpenELEC depends on a X.Y.Z versioning scheme this will be now (changes from now on are marked with (*)):
very big changes like a major update to XBMC. A automatic update from X-1 to X is not supported, a fresh installation is highly recommend.
Y. (Feature Release):
bigger changes to the Core OS, but usually not noticable by Users. This includes kernel changes, important changes and new features. (*) If Y = odd its a beta/testing build for Y+1 (even) releases. (*) Autoupdates from stable to testing (from Y (even) to Y+1 (odd))) is disabled, but enabled from testing to stable (from Y (odd) to Y+1 (even)) and stable to stable (from Y (even) to Y+2 (even)).
Z. (Bugfix Release):
bugfix releases to fix issues with older releases (Z-1) or simple changes like driver additions. Autoupdate is enabled from earlyer releases (Z-1 to Z)
This means our next stable release will beOpenELEC-3.2, which is based onOpenELEC-3.1 - our next testing release.
My guess is it means you can do it manually at your own risk. There is a wiki page on the XBMC wiki with issues for the upgrade to Frodo. The same will happen with Gotham, and since for example the whole way of creating settings is different, it will probably be best to start all over.
Or it might work.
That's why it won't be auto updated because otherwise it will be OE's fault, which is not the real cause of the problems
The administrator has disabled public write access.
Our (new) versioning scheme
4 years 6 months ago #6