[DOCS-14353] Investigate changes in SERVER-55725: Upgrade timelib to 2021.02 or later Created: 12/Apr/21  Updated: 13/Nov/23  Resolved: 24/Aug/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.0.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Dave Cuthbert (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-55725 Upgrade timelib to 2021.02 or later Closed
Participants:
Days since reply: 2 years, 43 weeks, 2 days ago
Epic Link: DOCSP-15042

 Description   

Description

Downstream Change Summary

There's an emphasis in our documentations to use the timezone database from MongoDB to workaround the timezone issue on operating systems that use the slim timezone format. However, with this change, this emphasis is not necessary anymore.

In addition, we need to backport this change into the earlier versions.

Description of Linked Ticket

The latest version of the timelib library includes support for so-called slim-format timezone data files, which previous versions could not correctly ingest. Since timezone data files will soon be distributed in slim format by default, it is important that we are able to properly recognise and process them. We should upgrade our embedded version of timelib to at least v2021.02 to ensure that we can do so.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


Generated at Thu Feb 08 08:10:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.