Tracking Issue: TimeZones 1.0

[nordzilla]

TimeZones 1.0

This aims to be a comprehensive tracking issue for all tasks left in order to consider time zones feature-complete in ICU4X 1.0.

If any new issues come up, I will be adding them to the list and tracking them here (or in a tracking sub-issue).

Useful Links

• UTS-35
  • [Date and Date Ranges]
  • [Date Format Patterns]
  • [Time Zone Identifiers]
  • [Time Zone Names]
  • [Using Time Zone Names]
• CLDR
  • [metaZones.json]
  • [primaryZones.json]
  • [territories.json]
• TZDB
  • [Olson/IANA Time Zone Database]

Criteria

• TimeZones 1.0
  • Tracking Issue: TimeZoneFormat #981
  • Tracking Issue: ZonedDateTime #1003
  • Tracking Issue: TimeZones DataProviders #992
  • Tracking Issue: Package IANA TZDB for ICU4X #1007
  • Tracking Issue: CLDR changes for TimeZones #1006

[sffc]

@nekevss is looking at Jiff, first it tries the OS, then it goes to the bundle.

I think we should try to use environment data. I would prefer not to own it but it is deeply integrated. Maybe we could start with defering users to a third-party crate. As long as we can get the time zone ID, the offset, and the zone variant (standard/daylight), we should have all the information we need. Then we don't need to block on the work of @leftmostcat and @nordzilla, but we can still continue developing in that direction to offer clients a more complete package.