It would be great if we could integrate the answers to the questions from dietrich's https://public.etherpad-mozilla.org/p/fxos-update-channels into https://foxfooding.github.io/
More specifically on the use-case, last night on a bug I found myself in the situation where someone using Firefox OS had a broken email app and AFAICT an out-of-date build, and trying to explain how they should update. And I had no idea. I checked out https://foxfooding.github.io/ and followed the OTA details link at https://foxfooding.github.io/2015/09/28/flame-system-partition.html to a bug that was duped to a fixed bug that was very confusing. I have no idea if things are okay for the Flame or not. So I linked to https://developer.mozilla.org/en-US/Firefox_OS/Phone_guide/Flame/Updating_your_Flame#Updating_your_Flame_to_a_nightly_build which is full of useful information, but is slightly terrifying and seems biased towards wiping out user data. It would be great if https://foxfooding.github.io/ could have an "how to be up-to-date" for Flame and Aries. And/or an "am I up to date" page, ideally one that does something like hyperlinks to https://foxfooding.github.io/am-i-up-to-date/#buildid=fromdevice&buildhash=fromdevice&release=2.5 and says stuff like "yeah, you're as up-to-date as it gets because of this OTA bug, but if you want to wipe out your data, you can totes manually flash this image". This would be doubly nice, because users could copy this link into bugzilla to ideally help me better understand what they're actually testing. It has always been a frustrating adventure to manually figure out if a bug reporter has the fix in their build already or not. Andrew PS: I know these are non-trivial asks and people are busting their butts to improve these scenarios. (And those people already have a lot on their plates and I am sending them positive thoughts even as I type.)
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
