Please temporarily specify promptWaitTime as 24 hours for Beta snippets

RESOLVED FIXED

Status

Release Engineering
Releases
P3
normal
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: akeybl, Assigned: bajaj)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Once we've had some bake time for bug 829222, and we've changed the in-product FF19 beta update backoff prompt to 48 hours, let's move forward with this change.

+++ This bug was initially created as a clone of Bug #829222 +++

We'd like to do the same for Aurora, once 829221 has a day of bake time on Nightly.

+++ This bug was initially created as a clone of Bug #829221 +++

When possible, please temporarily specify promptWaitTime as 6 hours for Nightly snippets. QA will verify that the update notification prompt occurs 6 hours after the update ping instead of the default 12. Once that verification is completed, and we've had a day or so of bake time, we can move forward with the bug to do similar on Aurora.
(Reporter)

Updated

4 years ago
Depends on: 829229
By the time this is ready, either
* we will have bug 823841 and specify it at release kick off time
* we won't have bug 823841, so *PRIOR TO KICKOFF* will manually modify
http://hg.mozilla.org/build/tools/file/default/release/patcher-configs/mozRelease-branch-patcher2.cfg
 near line 21 to add a new line
  promptWaitTime   86400

If we don't want to wait for the next beta then we can tweak a copy of the current betas snippets with ffxbld@aus3-staging:~/bin/add-promptWaitTime.py, and push them.

Tentatively blocking this on the b3 tracking bug, but to be advised by akeybl et al.
Blocks: 825309
Component: General → Release Engineering: Releases
Product: www.mozilla.org → mozilla.org
QA Contact: bhearsum
Version: unspecified → other
(In reply to Nick Thomas [:nthomas] from comment #1)
> By the time this is ready, either
> * we will have bug 823841 and specify it at release kick off time
> * we won't have bug 823841, so *PRIOR TO KICKOFF* will manually modify
> http://hg.mozilla.org/build/tools/file/default/release/patcher-configs/
> mozRelease-branch-patcher2.cfg
>  near line 21 to add a new line
>   promptWaitTime   86400
> 
> If we don't want to wait for the next beta then we can tweak a copy of the
> current betas snippets with ffxbld@aus3-staging:~/bin/add-promptWaitTime.py,
> and push them.
> 
> Tentatively blocking this on the b3 tracking bug, but to be advised by
> akeybl et al.

Beta 3 is starting today/tomorrow -- do we know if we want this for it? It'd be really helpful to know before starting the release.
(Reporter)

Comment 3

4 years ago
We're blocked on bug 829221, so this won't make b3.
Thanks for the update. Moving to b4 for now, maybe next week!
Blocks: 825310
No longer blocks: 825309
Blocks: 810319
No longer blocks: 825310
Blocks: 825311
No longer blocks: 810319

Updated

4 years ago
No longer blocks: 825311

Updated

4 years ago
Blocks: 825312
No sign of movement of bug 829221 or bug 829222 yet, so perhaps we shouldn't block this on a specific beta until they're resolved ?
(In reply to Nick Thomas [:nthomas] (gone 14-24 Feb PST) from comment #5)
> No sign of movement of bug 829221 or bug 829222 yet, so perhaps we shouldn't
> block this on a specific beta until they're resolved ?

Indeed. Doesn't look like this will make the 19.0 cycle at this point at all.
No longer blocks: 825312
(Reporter)

Comment 7

4 years ago
Correct, definitely pushed off till FF20. rstrong expects to investigate bug 829221 in the next week and a half.
Status: Waiting on dep bugs & FF20. When we're clear to go we'd specify promptWaitTime when starting the beta on ship-it.
This is 2 bugs down the blocking chain and doesn't look like it's going to happen anytime soon. P3 to get it out of the triage queue.
Priority: -- → P3
Depends on: 882007
Product: mozilla.org → Release Engineering
Assigning this to bajaj, as RelMan person for the current round of betas. Please use a value of 86400 in the 'Update prompt wait time' box in ship-it for Firefox (N/A to Fennec). AIUI we're still waiting for any feedback from Aurora.

FWIW, bug 906522 will make the helper comment on that page better.
Assignee: nobody → bbajaj
(Assignee)

Comment 11

4 years ago
The latest request for Fx24 Beta 7 has the Update prompt time : 86400 . Adding verifyme for QA to help with verification.
(Assignee)

Updated

4 years ago
Keywords: verifyme
on 24 beta 7, app.update.promptWaitTime is still at 48 hours (172800)
(In reply to Tracy Walker [:tracy] from comment #12)
> on 24 beta 7, app.update.promptWaitTime is still at 48 hours (172800)
The preference having a value of 172800 is intentional (bug 829229). This bug is about overriding that value and setting it to 24 hours via he update xml for beta.
ok, but https://aus3.mozilla.org/update/3/Firefox/24.0/20130829135643/WINNT_x86-msvc/en-US/beta/Windows_NT%206.1.1.0%20%28x86%29/default/default/update.xml?force=1 is empty. How do I check the override is correct?
nevermind. I figured it out. have to actually get an update so tested with 24beta6

 promptWaitTime="86400"
Keywords: verifyme
I'm dropping the promptWaitTime again as part of bug 1057460.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.