model-writtenrun 6072 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Andres Freund reported that the Windows subscription test failed under Greenwich Standard Time but passed under Pacific Standard Time, with unexpected one-hour differences in timestamp ranges #1.
- Tom Lane traced Greenwich Standard Time to the questionable Africa/Casablanca mapping and reproduced the failure on Linux, then identified interval subtraction crossing Morocco's 2014 Ramadan DST boundary as the test's immediate problem #4 #5.
- Tom replaced the interval calculations with explicit timestamp constants in 20f8671ef6, reported a successful check-world run under Africa/Casablanca, and received confirmation that Andres's Windows CI passed after removing its timezone workaround #8 #10.
- Thomas Munro pointed to CLDR's Windows zone data, prompting Tom's first attachment to correct numerous mappings, add missing zone names, replace aliases, and improve ordering; Tom initially chose Europe/London for Greenwich Standard Time and asked whether obsolete Windows spellings should be retained #7 #11.
- Tom subsequently recognized that Windows distinguishes GMT Standard Time for London from Greenwich Standard Time for places near the prime meridian, but initially retained the London mapping to accommodate likely user expectations; he also raised territory-aware mapping as a possible future improvement #12.
- Tom split the first attachment into the ordering-only commit ad740067ae and the mapping update 9b8d68cc65, retaining older zone names and adding UTC and offset corrections during his final review #11 #15.
- After that landing, Tom attached eight remaining differences from CLDR's default mappings and described two additional deliberate exceptions for Central America and Greenwich Standard Time, explaining that concern about politically sensitive choices had discouraged complete alignment #15.
- Thomas challenged the London exception, questioned the Samoa, Guam, and CET mappings, and recommended adopting CLDR's defaults consistently; he also suggested investigating modern locale names to obtain territory information #16 #17.
- Tom accepted that Reykjavik better approximated GMT because Iceland no longer observed DST, and discovered that Pacific/Samoa referred to American Samoa on the wrong side of the date line for Windows' UTC+13 Samoa zone #18.
- At the thread's last message, Tom withdrew the Central America exception after revisiting its history and announced that he would adopt all CLDR defaults absent objections; territory-aware mapping remained future work because it was unlikely to be backpatchable #22.
- The subsequent commit c1aa3b3c0d landed all eight attached follow-up changes plus the agreed Reykjavik and Guatemala mappings, completing the CLDR alignment discussed in #15 and #22.
- Finally, db692b0c84 updated src/timezone/README to make CLDR's territory=001 defaults the primary maintenance reference while retaining registry checks and compatibility with older Windows zone names, documenting the policy settled in #22.