[tz] proposal for new tzdb versions

Shawn Steele Shawn.Steele at microsoft.com
Thu Sep 23 18:03:20 UTC 2021

+1, it would be best if the 2021b had the minimal fix required to support the immediate timezone changes needed and defer additional cleanup/refactoring until the group has reached more of a consensus on how to handle the various concerns raised.


(I'll also confess to not having had time to catch up on ALL of the email flying around about this, however the passionate discourse by itself would seem to be an indication that we should take a step back and pause, making only the minimal changes required immediately.)

Message: 3
Date: Wed, 22 Sep 2021 11:52:20 -0700
From: Mark Davis ?? <mark at macchiato.com>
To: Tom Lane <tgl at sss.pgh.pa.us>
Cc: Paul Eggert via tz <tz at iana.org>
Subject: Re: [tz] proposal for new tzdb versions
	<CAJ2xs_E8TMP7bhsjnM4QCCTGKDd8SnqW3bh-Am0jab3yJq0x5g at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I agree with Tom's comments. We *really* don't want the disruption that would happen when some people pick up the 2021b and others pick up 2021a1; especially when it is likely that many of the people picking up 2021b won't know that they could be breaking downstream clients.

There is *no* harm at all to just issuing a 2021b that has 2021a + Somoan fix right now (no other changes). That is the simple option for now. Then people have the opportunity to hash out the situation without disruption.


More information about the tz mailing list