Closed Bug 1267002 Opened 8 years ago Closed 5 years ago

Update the Windows 10 base image for testing to build 10586 (November Update)

Categories

(Infrastructure & Operations :: RelOps: Windows OS, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: RyanVM, Unassigned)

Details

We recently started collecting better Telemetry data about which versions our Windows 10 users are on. The results so far indicate that they are overwhelmingly on the November Update (80+% - see the bottom pie chart):
http://nbviewer.jupyter.org/urls/s3-us-west-2.amazonaws.com/telemetry-public-analysis-2/windows-distribution/data/windows-build-distribution.ipynb

So far, this data only covers Nightly and Aurora. Next week we'll see what the Beta population looks like once Gecko 47 moves up a train (though I suspect the number of users on a current version will actually go up as we get to a less-savvy population given how MS makes opting out non-trivial).

Also interesting to me is that it shows pretty clearly that Microsoft's update strategy is working out pretty well for keeping users up to date. Over 92% of the users on build 10586 are on the April cumulative update released a couple weeks ago. Not sure how feasible it's going to be for us to keep that semi-current in CI, but it at least suggests to me that it'd be worth keeping in mind.
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations

hi Mark, can you please check this ?

Component: CIDuty → RelOps: Windows OS
Flags: needinfo?(mcornmesser)

This is old. There is working being done to upgrade to Win 10 1803 which is the update that came out last April.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(mcornmesser)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.