On Sat, 3 Oct 2026 at 14:58, Brian Inglis via tz <[email protected]> wrote:
> Anyone know what's the status from the folks at Apple and Oracle? We don't tend to hear anything or get any advance insights from them, but I am starting to wonder the extent to which there'd be value in starting to track major vendors' follow-through. Showing a fuller view of the data lifecycle with hard numbers on a page like my https://tzdata-meta.timtimeonline.com/ might be a useful artifact to point to. FWIW, Apple's latest push is 2026c, which made it to devices about three weeks after our release. While we just passed the three-week mark for 2026d, its only contemporaneous data change was America/Inuvik and 2026e has just come out in the meantime, so it's quite possible that has "restarted" Apple's testing "clock", so to speak. In particular, I could see a desire to avoid pushing out anything that says "time zone update" to endusers who might be in Manitoba without it including Manitoba's change. It's another weight on the scales in favor of batching data changes, and just emphasizes how much everything is always a judgment call on opposing interests when it comes to our release contents and timing. At the time, we felt we'd already held back on Inuvik about as much as we reasonably could, but had we known about Manitoba's impending change or had it happened a week earlier, the situation could've been entirely different. Hindsight may be 20/20, but time only moves forwards — except, of course, when it doesn't. ;) While we had originally intended for a day or so for review, given the ongoing discussion, we ultimately decided to release a bit more quickly in the hopes that an earlier-in-the-week release could help the major vendors get a start on turning their respective cranks in what was left of this past week, rather than next. https://lists.iana.org/hyperkitty/list/[email protected]/message/MPKTOSLQVEWYPS4GOGL6ZV7T4C3NHHR3/ -- Tim Parenti
