"I want to see information on release before upgrading" I think it means, on Firefox OS devices, users can see information about the update before they agree to do the upgrade, right? In this case, do we need to take localization(regarding to the information presented to users) into consideration in this version? Thank you.

"I want to have a rollback solution (1 version back)" This sounds very vague to us now. After discussing with engineering teams, we would like to propose the following scope: 1. To focus on full package rollback only. It means, Gecko/Gaia update is not covered. 2. To clear all data after doing the rollback. And, we assumed the device can be booted before doing the rollback. Here, some questions for you: 1. Why are we going to implement this rollback feature, while other OS don't support? 2. Can you accept the above proposed scope for rollback? Thanks, Wilfred.

Some thoughts about rollback here: 1) If 'rollback' specifically refers to reverting to the 'version before the last update', making a backup might be the simplest but the safest approach. We can have a system wide 'backup' event for each component to hook its own necessary backup. 2) If 'rollback' also refers to 'downgrade'ing to arbitrary old version, it would be much more complicated and even backup couldn't help.

(In reply to Kevin Hu [:khu] from comment #1) > "I want to see information on release before upgrading" > > I think it means, on Firefox OS devices, users can see information about the > update before they agree to do the upgrade, right? In this case, do we need > to take localization(regarding to the information presented to users) into > consideration in this version? > > Thank you. For this part specifically, you can maybe take a look at https://bugzilla.mozilla.org/show_bug.cgi?id=834462

Thanks! Clément. Bug 834462 looks like one piece we can meet this acceptance criteria. Let me add the dependency here.

"I want to have updated only for Foxfooding devices." Wilfred, does it mean we don't want to provide update for non-foxfooding devices? Thank you.

"I want to have updated only for Foxfooding devices." I would like to receive Gecko/Gaia updates directly from Mozilla on a device I ported myself. Assuming it passes QA for community builds. What's the equivalent to Android CTS?

It could be useful to at least know what comes from Mozilla and what comes from partners, so that we could know from where is the problem: https://bugzilla.mozilla.org/show_bug.cgi?id=1123621

Since we are clarifying the scope now, it might be better to set the owner to the product manager. Wilfred?

So - realistically, I don't see any practical way of rolling back an update that was performed by FOTA. We can't rollback updates that were updated by any other mechanism than our own OTA. The only place we're using our own OTA is on our foxfooding devices. Since all of the data on the phone is going to be wiped anyways, you can achieve the same result by doing a full flash of any previous version which is available.

Let's revisit the acceptance criteria for 2.5 scope: I want Mozilla to host upgrade paths => OTA path is existing feature I want to have a rollback solution (1 version back) => remove this one? I want to see information on release before upgrading => bug 834462, should be scheduled in 2.5 timeline. I want to have updated only for Foxfooding devices. => OTA path is existing feature I want Mozilla to provide a full update for my foxfooding device (gaia/gecko/gonk) => FOTA is existing feature

I guess that the "Mozilla to host upgrade paths" is more about devices Mozilla isn't managing updates (ie. partners): ZTE (Open, Open C, incoming Open L), Alcatel, Geeksphones devices and so on. For now Mozilla only managed for devices like Unagi, Flame, Now the Xperia like Aries, Leo and some others as far as I know. But it would be really nice to see Mozilla manage OS updates on partners devices, even if I guess very difficult for them to accept this. Same about some devices not sold with Firefox OS but with builds for them.

switched the ni to Andrea for finalizing the 2.5 scope

2.5 scope updated below: I want Mozilla to host upgrade paths => OTA path is existing feature I want to have a rollback solution (1 version back) => remove this one? [A.A.] Not in the scope for 2.5. However this requirement is still valid beyond 2.5 I want to see information on release before upgrading => bug 834462, should be scheduled in 2.5 timeline. I want to have updated only for Foxfooding devices. => OTA path is existing feature [A.A.] This has to be in the scope for 2.5 as we should have a methodology in place to limit FOTA updates to internal foxfooders (we cannot allow FOTA outside internal foxfooders due to concerns from legal). E2E process of whitelisting internal foxfooders devices need to be discussed and reviewed. I want Mozilla to provide a full update for my foxfooding device (gaia/gecko/gonk) => FOTA is existing feature

(In reply to aaime from comment #14) > 2.5 scope updated below: > > I want Mozilla to host upgrade paths > => OTA path is existing feature > > I want to have a rollback solution (1 version back) > => remove this one? > [A.A.] Not in the scope for 2.5. However this requirement is still valid > beyond 2.5 > > I want to see information on release before upgrading > => bug 834462, should be scheduled in 2.5 timeline. > > I want to have updated only for Foxfooding devices. > => OTA path is existing feature > [A.A.] This has to be in the scope for 2.5 as we should have a methodology > in place to limit FOTA updates to internal foxfooders (we cannot allow FOTA > outside internal foxfooders due to concerns from legal). E2E process of > whitelisting internal foxfooders devices need to be discussed and reviewed. Bug 1201538 , bug 1201556 attached for this. > > I want Mozilla to provide a full update for my foxfooding device > (gaia/gecko/gonk) > => FOTA is existing feature

Firefox OS is not being worked on