Date: Fri, 6 Mar 2026 16:56:10 -0800
From: Paul Eggert <[email protected]>
Message-ID: <[email protected]>
| > This looks to me not to really be a "hurry and make a change so it can
| > operate next week" but "hurry and make a change that will apply towards
| > the end of the year, but needs to be made now before our authority to do
| > it is removed".
|
| Not sure what is meant by "authority" but that is not the motivation.
No, that's a misunderstanding of what I meant, probably my fault. I meant
the change made by whoever made it in BC - from what I read (here, on this
list, so it may be incorrect) they wanted to make the change, to be effective
in November this year (or whenever the next return to standard time was to
occur) but were not assured of being able to make any change for much longer
(after now), so they legislated it now, with the intent (which seems clear
in what I have read of the wording) to have practical effect from November
(or ...). That is, no immediate change needs to occur, everything remains
as it was, for all practical purposes, until the subsequent change.
What will break exactly, if nothing in tzdata is altered for this for
a month or three?
| The motivation is that it's better to change TZDB before the events it
| describes, rather than changing retroactively. Obviously we can't always
| be proactive, but proactive is better when possible.
Certainly, so a tzdata update for this, sometime in the next few months
(say by May or June or so at the latest) would seem like a wise choice -
once things have had more time to settle. I don't see anything being
required in the next few weeks. For all we know, some "higher power"
might override this planned change.
| > your desire to follow the letter of the law is kind of quaint,
| > given that you changed "EST"
|
| Oh, please, let's not let old beefs derail solutions to new problems....
It is all about precedents. Either the local laws are important, or they
are not, you decide which of those applies, and apply that consistently.
kre
