Page MenuHomePhorge

Update external timezone information
ClosedPublic

Authored by aklapper on Jan 27 2024, 08:33.
Tags
None
Referenced Files
F3001443: D25529.1740442133.diff
Mon, Feb 24, 00:08
F3001442: D25529.1740442132.diff
Mon, Feb 24, 00:08
F2997994: D25529.1740407359.diff
Sun, Feb 23, 14:29
F2997464: D25529.1740398432.diff
Sun, Feb 23, 12:00
F2995488: D25529.1740343300.diff
Sat, Feb 22, 20:41
F2995487: D25529.1740343296.diff
Sat, Feb 22, 20:41
F2987198: D25529.1740110750.diff
Thu, Feb 20, 04:05
F2982280: D25529.1739948796.diff
Tue, Feb 18, 07:06

Details

Summary

Update the list of timezones from 2016 by pulling from CLDR upstream (revision 57c1f4c from 2024-01-11) located at https://github.com/unicode-org/cldr/blob/main/common/supplemental/windowsZones.xml

Closes T15727

Test Plan

Diff Detail

Repository
rP Phorge
Branch
windowsTimezonesUpdate (branched from master)
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 1047
Build 1047: arc lint + arc unit

Event Timeline

I admit I did not test what happens when setting a (deprecated) timezone in Phorge to be removed by this patch, and then applying this patch.

This revision is now accepted and ready to land.Jan 27 2024, 10:19

I admit I did not test what happens when setting a (deprecated) timezone in Phorge to be removed by this patch, and then applying this patch.

Answering to myself: This is just a mapping. Even though the "old" version from 2016 still contained "Pacific/Johnston", that item was not listed as an option anyway on http://phorge.localhost/settings/panel/datetime/ before applying this patch on my system (due to a recent tzdata system package used by PHP).

This revision was automatically updated to reflect the committed changes.