Open Bug 1761070 Opened 4 years ago Updated 3 years ago

Reduce the app.update.promptWaitTime value for Aurora and Beta

Categories

(Toolkit :: Application Update, task, P5)

task

Tracking

()

People

(Reporter: RyanVM, Unassigned)

References

Details

(Whiteboard: [fidedi-ope])

Attachments

(1 obsolete file)

The current value of app.update.promptWaitTime (8 days) goes back 6 years to bug 1268340. Since then, we have made significant changes to both how we notify users of available updates and the duration and cadence of our Beta releases. Users only being prompted about a pending update every 8 days is nearly 1/3 of the total cycle length and potentially limits our ability to get timely feedback from that audience.

Given our current build cadence of every 2-3 days, I propose a new value of 3 days and will submit a patch for that. Note that I'm not proposing changes to the Release value at this time, though I'm certainly open to changing it also depending on Product's thoughts on the matter. Romain? :-)

Flags: needinfo?(rtestard)

Given Beta's nature and build cadence change the proposed new value makes sense to me.
Regarding release I'd like some time to look into how many users currently see the prompt and how this would change based on value changes - we need the right balance between avoiding to annoy users (having to restart Firefox is a painful process if you don't have session restore enabled, which is most user situation) and ensuring updates are applied in a timely manner to ensure security patches and features are deployed.

Flags: needinfo?(rtestard)

I think that this may be reasonable on the Beta channel, but I would really like to weigh in against decreasing promptWaitTime on the Release channel. We know from uninstall surveys that our update prompts drive users away. Because of this, our team has been working for some time to figure out how to make it safe and reasonable to increase promptWaitTime.

The Beta channel does largely exist to get feedback from our users before we release a version of Firefox. But this same argument doesn't really hold up for the Release channel. So if we are going to consider such a change for that channel, I would like to better understand the reasoning for doing so.

Component: Preferences → Application Update
Product: Firefox → Toolkit

I have no problem with punting the Release question to a different bug if we want to leave this one focused on the Beta/Aurora changes that seem less controversial :)

Attachment #9269101 - Attachment is obsolete: true

Based on the comments in D141880, the patch I attached isn't the approach we want to take to solve this bug, but I'm afraid I don't have the cycles to pursue the more generic approach being proposed.

Assignee: ryanvm → nobody

I'm going to try to look at this in the next month or so - I've been looking for something update related to get my feet wet there anyways.

Assignee: nobody → bhearsum
Severity: -- → S3
Priority: -- → P2
Whiteboard: [fidedi-ope]

P5: we'd take a patch.

Priority: P2 → P5
Assignee: bhearsum → nobody
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: