While advocating for a year's notice or any change, can I advocate that any release of timedata is also a year in advance of that change. Airlines take advance bookings up to 360 days of first outbound travel and so a late released change can mean late rescheduling of flights, updating of tickets, potentially rebooking of tickets where connections no longer connect.
In the past releases have been considered not urgent, but this change is much more significant due the size of the market being impacted. On Wed, 29 Jul 2026 at 07:22, Paul Eggert via tz <[email protected]> wrote: > On 2026-07-28 11:19, Brooks Harris wrote: > > I think the better approach is permanent standard time. If that came > about it's a very simple technical matter of just stopping DST and > everything flows fairly naturally from there. The Committee should also be > aware how that option would greatly simplify technical issues. Am I right > about that? > > In any hypothetical conversions with Senate staff I am not planning to > advocate whether to go to permanent standard time, or move one time zone > east (a.k.a. "permanent daylight saving"), or doing nothing - other than > perhaps the obvious point that doing nothing is simplest technically. I > don't want these larger issues to drown out the importance of a year's > notice of any timekeeping changes. As I understand it we're united on > needing a good long notice, even if we may disagree on which timekeeping > change, if any, is advisable; and I want to focus on where there is pretty > much universal technical agreement. >
