We should start to expand the warning for older versions of Firefox on SUMO. we are still only showing this to users on 3.6 and below, and Firefox 12-16, correct? We should start to expand this (even a low CTR is better than no CTR). I'm proposing the following: <=16 (ESR 10 is no longer supported) 18-23 (ESR 17 is still supported and ESR 24 is coming online) We have run several studies of uses and find that roughly 80% of them want to be up to date, but either assume they are already updated automatically (but aren't due to a failure in the updater, user permissions, or something else), or just turned updates off at some point in the past or don't use Firefox enough to have it check for updates. I haven't seen any evidence this banner annoys users, and honestly, users on very old systems have no right to be annoyed at getting warned they have an out of date and unsupported version of the software when visiting said software's support site. We don't have to roll out to the most recent versions (so we don't have to warn on 22 and above if you'd like) but we should implement a policy of continually updating this list as new versions roll out.

From https://bugzilla.mozilla.org/show_bug.cgi?id=651230#c31 I think we should show it everyone not on the latest but we should be two weeks behind the release schedule. In other words Fx 20 users won't see the message until two weeks after 21 is out. Most people will update by then.

Based on Tyler's comment I think that we should go with Verdi's recommendation. My 2 cents... It doesn't look like the implementation is annoying anyone and we could become a good source of upgrades.

In a PR. https://github.com/mozilla/kitsune/pull/1685 While I did discuss doing something more automated and a bit smarter than manually updating this list every release with mythmon at the summit, this at least get's all these releases that aren't currently receiving a notification (a not insignificant number) on our warning for now.

Landed on master: https://github.com/mozilla/kitsune/commit/aa09725cda4c96eceb4dcf9eb8d4777a3ce03598 Thanks Tyler!!

Deployed to prod.

Well it works but it seems mozilla.org is less aggressive then we are. Using Firefox 23.0.1 I visited support.mozilla.org and got the out of date warning. If I click the upgrade button I'm taken to a mozilla.org page that says, "Congrats! You’re using the latest version of Firefox."

That's interesting, and we should file a bug ;) Can you do that with the URL you saw the "up to date" message on? I'm going to guess that was an oversight since we have started to be a bit more aggressive with that messaging AFAIK

Michael - did you end up on /update or /new to see the "Congrats you are up to date" message?

(In reply to Jennifer Bertsch [:jbertsch] from comment #8) > Michael - did you end up on /update or /new to see the "Congrats you are up > to date" message? I end up on /new

Out of curiosity, I went to /update to see what's there and I get a message that says, "Your Firefox is out of date. Get the newest version here." That takes me to /new which says I'm up to date.

LOL *head on keyboard* I'll discuss that one with Cmore and Holly.

We are pointing to /new/ so maybe we need to change that to /update? We should all align our strategy here. Moz.org considers Currentversion - 1 to be up to date to avoid the problems around throttling and chemspills. I don't see a major problem adopting that for now, until we have a better solution.

We are planning to delete /update since /new is now handling that messaging.

(In reply to Jennifer Bertsch [:jbertsch] from comment #11) > LOL *head on keyboard* I'll discuss that one with Cmore and Holly. This is expected behavior. Latest version is calculated as current version minus one and not including ESR builds on the /firefox/new/ page. The /firefox/update/ page is a legacy page that is soon going away and will be redirected to /firefox/new/. I am filing the bug now to have /firefox/update/ redirected to /firefox/new/. The code for latest version - 1 on /firefox/new/ is here: https://github.com/mozilla/bedrock/blob/master/media/js/firefox/new.js#L21 The reason we added that is because it is possible that someone has silent updated and just hasn't restarted their browser. Having them download and install again is a waste of time even though it would force a restart. The code for the /firefox/update/ does not subtract 1 and thus the weird behavior. Filing a bug to have /firefox/update/ redirected to /firefox/new/.

(In reply to Ibai Garcia [:ibai] from comment #12) > We are pointing to /new/ so maybe we need to change that to /update? > > We should all align our strategy here. Moz.org considers Currentversion - 1 > to be up to date to avoid the problems around throttling and chemspills. > > I don't see a major problem adopting that for now, until we have a better > solution. There is also another reason for the current version -1. It is because of a silent update occurring, but a user not restarting their browser to have it applied. We are pushing to see if it is possible to have mozilla.org whitelisted to allow JavaScript to detect that an update is applied and they just need to restart to have it applied.

(In reply to Verdi [:verdi] from comment #6) > Well it works but it seems mozilla.org is less aggressive then we are. Using > Firefox 23.0.1 I visited support.mozilla.org and got the out of date > warning. If I click the upgrade button I'm taken to a mozilla.org page that > says, "Congrats! You’re using the latest version of Firefox." I can reproduce this on my Android tablet. I have auto updates off in the play store so im on an older version. 22/23. I'm told out of date through sumo, then when I go to update, I'm taken to you're up to date.

(In reply to Andrew T. [:feer56] from comment #16) > (In reply to Verdi [:verdi] from comment #6) > > Well it works but it seems mozilla.org is less aggressive then we are. Using > > Firefox 23.0.1 I visited support.mozilla.org and got the out of date > > warning. If I click the upgrade button I'm taken to a mozilla.org page that > > says, "Congrats! You’re using the latest version of Firefox." > > I can reproduce this on my Android tablet. I have auto updates off in the > play store so im on an older version. 22/23. I'm told out of date through > sumo, then when I go to update, I'm taken to you're up to date. Yes, that is true. I will talk to the team if we want to take the same current version - 1 approach for Firefox on Android since updates happen more seamless than desktop and there are prompts.

We have to update this again, since Firefox 25 is now the latest version. But before we do that, given what Chris said, I'm assuming we should also do currentversion - 1. Any objections?

yes, currentversion -1 is the policy going forward.

Some users have reported that the version check behavior confused them, so we are removing the -1 logic from www.mozilla.org. (Bug 935673) The SUMO team may want to replace the manually-updated version check with the Update Bar, which will soon be implemented as a Tabzilla extension. (Bug 935719)