Sept. 20, 2021
1:34 p.m.
Stephen Colebourne via tz <tz@iana.org> writes:
In the event that the tzdb maintainer does not revert, consideration must be given to forking the project. The purpose of the fork would initially be to maintain the tzdb data set as it was prior to the dispute. This would then be released in parallel to the original tzdb to ensure that downstream projects do not each do their own thing (ie. to minimize incompatibilities downstream).
It pains me to say it, but since there apparently is no willingness to revert that decison, a fork is going to be necessary. I support this, and it is likely that the Postgres project would follow the fork. regards, tom lane