-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.4.0
-
Component/s: Aggregation Framework, Querying
-
Query Execution
-
Minor Change
-
v6.3, v6.0, v5.0, v4.4
-
QE 2022-10-31, QE 2022-11-14, QE 2022-11-28, QE 2022-12-12, QE 2022-12-26, QE 2023-01-09, QE 2023-01-23
-
(copied to CRM)
There has been a new release 2022g of timezone files. We should consider upgrading the builtin timezone rules, and potentially backporting.
This release includes the move of Mexico away from supporting DST (Daylight Saving Time)
Update: The original request was to update the built-in timezone files but it's preferred to upgrade a third party library as a whole for all third party libraries if there's an official release so as to avoid any hassles (mostly resolving merge conflicts between custom changes and vanilla version) to deal with custom changes to each third party library. So, we upgrade the whole timelib instead of updating only the built-in timezone files. But note that the timelib owner does not release a separate version for each timezone db release. So, probably we need to update timezone files only when there's no separate release. Still it would be worth asking the timelib owner whether he's willing to release a separate version even though there's no separate release yet.
- causes
-
SERVER-78750 Fix Olsen timezone script to refer to the new timelib directory
- Closed
- depends on
-
SERVER-44273 Failure to parse certain time zone specifications on windows platforms.
- Closed
- is related to
-
SERVER-90147 Upgrade timelib.h to 2022.10 and timezone files to 2024a
- Closed
- related to
-
SERVER-55725 Upgrade timelib to 2021.02 or later
- Closed
-
SERVER-60141 Upgrade timelib to 2021.09 or later
- Closed