Thanks a lot for all the information. I am sure IATA, airlines and OTAs use other systems to handle the timezone information. But in our case we rely on TZDB for this. We connect to airline and OTA APIs that in most cases do not provide flight duration information. We only get flight departure and arrival times and with these local times (maybe in different timezones) we calculate flight durations. This is why we are currently impacted by Paraguay timezone rules change, because the airlines are using the updated rules while our system is (was) not yet updated. Any system that works with future events that has to convert them between UTC and local time, or between different time zones is impacted by not having the right rules for the next months. In our case we handle events (flights) up to more than one year in advance. So, my point was, do not think that it is OK as long as you publish the TZDB with enough time for its propagation to the operating systems, Java, etc. The sooner we get the updated rules the better for this type of application handling future events. We have manually ported Paraguay rule to our TZDB thanks to the development repo that you linked. Thanks a lot for your help. On Fri, Dec 20, 2024 at 9:24 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
On 2024-12-20 00:10, ofrias--- via tz wrote:
Is there an estimated date when this change will be published?
We should publish the next TZDB release sooner rather than later, because of Paraguay. We don't have an estimated date, though.