Closed
Bug 1558272
Opened 7 years ago
Closed 7 years ago
Add Windows 10 May 2019 Update to WindowsVersion.h
Categories
(Core :: MFBT, task, P1)
Tracking
()
RESOLVED
FIXED
mozilla69
People
(Reporter: bugzilla, Assigned: bugzilla)
Details
Attachments
(1 file)
|
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
Build 18362.
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → aklotz
Status: NEW → ASSIGNED
Priority: P3 → P1
| Assignee | ||
Comment 1•7 years ago
|
||
Pushed by aklotz@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/20c4d3173a63
Add Windows 10 May 2019 Update to WindowsVersion.h; r=dmajor
Comment 3•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Comment 4•7 years ago
|
||
Comment on attachment 9071050 [details]
Bug 1558272: Add Windows 10 May 2019 Update to WindowsVersion.h; r=froydnj!
Beta/Release Uplift Approval Request
- User impact if declined: Possible footgunning down the road if we uplift patches to ESR68 which depends on this detection being in place.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is essentially zero risk. It's just adding detection for the latest release of Windows 10. I'm hoping we can take this now while we're thinking of it so it's not a footgun waiting to burn the trees if we have to uplift a patch to ESR68 which makes use of this sometime during its lifecycle.
- String changes made/needed:
Attachment #9071050 -
Flags: approval-mozilla-beta?
Comment 5•7 years ago
|
||
Comment on attachment 9071050 [details]
Bug 1558272: Add Windows 10 May 2019 Update to WindowsVersion.h; r=froydnj!
fair enough. will be in 68.0b10
Attachment #9071050 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 6•7 years ago
|
||
| bugherder uplift | ||
status-firefox68:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•