823525 - Should we turn the 3rd party app updates feature off for v1?

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia::System, defect)

Description

[Jason Smith [:jsmith]]

So...basically the smoke tests of this feature have failed pretty badly. Such issues include:

* bug 823403 - the status bar gets hung on an update
* bug 823189 - the packaged app fails to launch after updating
* bug 823150 - the update notifications don't fire over 45 min after a manual sync
* bug 822870 - process restart required to get app updates
* bug 822855 - no update notifications for hosted apps

However, initial triage basically minused every single bug, although they have all been sent back into triage since to my understanding, this was a critical v1 feature. If they get minused again, then I think we have to consider turning the feature off for v1 either partially or fully - more for the packaged app update experience, given the severity of the bugs found. The specific example that is probably the showstopper on this is the fact that applying an update to an app right now basically makes it impossible to launch, which means the app update experience is more of a problem than a benefit right now.

Product needs to make a call if they still want this. But if we aren't fixing critical bugs associated with the feature then I think it needs to be cut from v1 and turned off.

Comment 1

[Jason Smith [:jsmith]]

Product decision needed. My opinion is that I would fix the blockers and not turn the feature off, as I originally thought this was kinda of an important feature. But if we're leaving behind bad bustage on smoke tests for v1, then there's no point to leaving this feature entirely on for v1.

Comment 2

[Jason Smith [:jsmith]]

Resolved in triage. The one bug has now been marked as a blocker and other contention has been resolved.