[tz] Magallanes region from Chile will keep DST all year round

Deborah Goldsmith goldsmit at apple.com
Wed Jan 25 16:13:30 UTC 2017

It’s not just the TZ database itself. There’s also:

1. ICU metazone information (both Google and Apple use ICU)
2. Time zone geographical information (for automatic selection)
3. Localized names for time zones and/or cities within them (for manual selection)

When just the behavior of existing zones is modified, then updating TZ and ICU is enough. When new zones are added (by splitting existing zones), there’s a lot more subsidiary information that needs updating.


> On Jan 25, 2017, at 2:36 AM, John Haxby <john.haxby at oracle.com> wrote:
> On 24/01/17 19:51, Deborah Goldsmith wrote:
>> The point is, many TZ clients (not just Apple, not just ICU) consider a change that takes effect in 3 1/2 months “urgent.” It is not just a matter of development cycles; it’s also a matter of release cycles.
>> There are some TZ clients who can turn a change around in a few days, and there are some that require much more lead time. Telling the latter that it’s their problem they have a different business model from the former is not productive.
> I'm with one of the "turn a change around in a few days" distros but I
> have every sympathy with you Debbie.   Sometimes even a few days isn't
> fast enough -- we've had some people demanding an update on the basis of
> a rumour before now and, of course, some countries are fond of changing
> the DST rules with next to no notice.
> RFC7808 (tzdist) hit the streets in March 2016 and I've been waiting
> with bated breath to see it actually implemented anywhere.  I've turned
> an interesting shade of blue now, but I'm still hopeful[1].
> Roll on tzdist ...
> jch
> [1] One of the authors of RFC7808, Cyrus Daboo is also from Apple so I'm
> hopeful that Apple will turn out something soonish, perhaps in Autumn?
> Fingers crossed.

More information about the tz mailing list