Hi folks.
Sorry for being late. I want to add two thought to the discussion: one is about
service workers. For educational purposes, I want you to take a look at
`offliner` [1] a toy library using Service Workers (in Chrome Unstable) I
implemented for the Portland event, past December. It's as
Hey,
my provocative question for the day: Why do users still have to flash
new base images on their own? Wasn't Flame the phone we've been promised
real updates for?
Constantly flashing baseimages my own is surely even more irritating to
non-Mozillians.
___
FWIW, all Flames that were flash at MozFest (around 800 devices I think)
have the v180 base image on it. Not many people will have updated to
v188 on their own I guess.
Regards,
Michael
--
Michael Kohler
Mozilla Rep - https://reps.mozilla.org/u/michaelkohler/
Mozilla Switzerland - https://twitte
+Wesly, as he's the TAM working with T2M.
T2M has a different update server than we do. Legally we cannot distribute the
gonk layer.
This means that we need T2M to host the update. However if you update with our
gecko and gaia, you will get our OTA server, not theirs.
We are trying to work wi
All work was completed on Monday and services fully restored. If you are
experiencing any issues, please contact #vcs.
NOTE: if you use the remote git.mozilla.org/integration/gecko-dev.git
please keep reading.
If you use this particular remote, and pulled during the problem window
(roughly J
Thanks Naoki and Michael's information sharing!
And Frederik, we have 1-time FOTA for Flame that was released by T2M : )
Since the SW shipped with Flame is v123 (FxOS 1.3, JB), the FOTA we worked
with T2M is for user with that SW to upgrade to v188 (FxOS 2.0, KK), this
is released on Nov./10 last
