Closed Bug 1170482 Opened 5 years ago Closed 5 years ago
Update internal timezone database to version 2015e
AFAIK Lightning contains timezone definitions based on 2015a release. The latest release is 2015d and based on the release notes the timezones for Egypt, Mongolia, and Palestine were changed. We should include this changes.
If we want to do this for 4.0 we'd need to patch it asap, release builds are likely being created soon.
These were all the changes our script does. Please double check that there are not more changes and our script needs bugfixing. Unfortunately I don't think we can include this for 4.0, the release builds are going to build asap. If you have time this weekend, maybe we can still push it in before the release builds start.
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Attachment #8616370 - Flags: review?(ssitter)
Comment on attachment 8616370 [details] [diff] [review] Fix - v1 r=me, sorry for the delay Could you do a comparison with 2015e and incorporate changes if necessary? Reading comment in update-zones.py it seems this can be run on Linux only but not on my Windows build system.
Attachment #8616370 - Flags: review?(ssitter) → review+
Yes, I'll take a look. Which comment are you referring to? I haven't tried update-zones.py on windows, I guess there may be some path issues.
Pushed to comm-central changeset 0ca6d3c3d328
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 4.3
Summary: Update internal timezone database to version 2015d → Update internal timezone database to version 2015e
Backported to releases/comm-aurora changeset dcf4f0f25630
Target Milestone: 4.3 → 4.2
Backported to releases/comm-beta changeset 9ae9dd17eade
Target Milestone: 4.2 → 4.1
Backported to releases/comm-esr38 changeset 0a8bc3e3919c
Target Milestone: 4.1 → 4.0
You need to log in before you can comment on or make changes to this bug.