[tz] Uruguay out of DST
goldsmit at apple.com
Fri Jul 10 16:15:11 UTC 2015
It’s certainly appropriate to verify the data is correct before releasing it. I was responding to the idea that there’s no rush to release it. It’s important for many companies for IANA to release the data as soon as possible, so there is time to integrate it. As someone else pointed out, delays can cause new data to miss a release and have to wait for the next one. That can make the difference between being in time for a change, and not being in time.
Let me rephrase: is there any reason to wait once the data is verified? Is there anything we can do to increase confidence in this particular change?
> On Jul 10, 2015, at 12:05 AM, Paul Eggert <eggert at CS.UCLA.EDU> wrote:
> On 07/09/2015 10:08 AM, Deborah Goldsmith wrote:
>> Is there an advantage to waiting?
> Yes. After we make a change, sometimes we find that the supplied information was wrong. Sometimes the authorities change their minds. Sometimes we have the correct information but enter the data incorrectly, and don't discover this until further review. In cases like these, dallying before an official release can save us all some work. This is partly why we delayed from March 10 to March 21 before releasing 2015b as an official fix for Mongolia.
> If these delays cause problems for you, it's reasonable to use the unofficial repository at <https://github.com/eggert/tz> as a basis for operating system patches. That is, users of the tz database have a choice of either a bleeding edge unofficial version that is more up-to-date but is also more likely to contain errors, or a more-stable official version that may not have the very latest experimental changes but should work well for those who keep reasonably up-to-date with the official version.
More information about the tz