Even for scheduling systems, some historical time zone data may still be needed. Consider if you have a recurring task in a time zone that has an upcoming standard offset change or DST rule change. Before the change, you only needed to know that it was coming up. But as soon as the change has come into effect, the old rules are now the "historical data". Sure - you might* not need the old rules for scheduling the next occurrence, but your application may have other reasons to reference the old rules (reports, etc.)
* I've also worked on some scheduling systems where the original first occurrence date is kept in terms of local time, and future dates are based on that original date. In this case, the old and the new rules must both be available to schedule any future occurrence. On Mon, Nov 3, 2025 at 11:51 AM Tim Parenti via tz <[email protected]> wrote: > > On Mon, 3 Nov 2025 at 14:45, Guillermo Rodriguez Garcia < > [email protected]> wrote: > >> for my application (an embedded >> system that needs to schedule events) historical data is completely >> irrelevant. > > > That is a valid case and it will likely work well for you, then! As it is > more the exception than the rule, though, I feel it's important to > occasionally remind others reading the list that, like with many things in > life, there's no such thing as a one-size-fits-all solution. > > -- > Tim Parenti >
