On 2024-12-20 01:10, ofrias--- via tz wrote:
As you mentioned, this is an unimportant patch since it affects only
tm_isdst. What matters is that we publish a new TZDB release well before
March, when the main Paraguay change occurs. We can include in that
release any other changes that come down the pike soon in the
Philippines or Ukraine or whatever.
Please take into account that in some applications timezone rules are used well before the timezone rule change date.
It is up to civil political administrations to take into account required
considerations, including notification lead time, as they are mandated by
international aircraft operating scheduling rules to publish notices of any time
changes with adequate lead time.
If civil political administrations do not publish notices of any time changes
with adequate lead time, they are punished by penalties of millions of taxpayer
money (backed by the threat of stopping scheduling flights into their
territories), depending on the impact of any disruption to schedules, and likely
business impacts of reschedulings and cancellations of many flights, as airports
and airlines, and their operational systems, can not be changed nor change their
operations, as quickly as politicians change their minds, after failing to make
up their minds for months!
For example, I am writing from the flight metasearch website Trabber.com and we use timezones to calculate flight durations.
Trip durations depend only on route locations and directions not clock times and
should be fixed - except for real time operational, weather, and "traffic"
disruptions - they should never be calculated!
Departure times should be stored only for trip origin locations, in local or UTC
depending on whether the departure occurs at a fixed local or UTC time, and in
the latter case, changes after DST changes.
See the IATA SSIM guidelines and notices for airlines, airports, and civil
authorities regarding scheduling and notifications requirements and best practices.
So currently all flights to/from Paraguay from April 2025 onwards are displayed
with a wrong duration because our TZDB is not updated yet.
What really matters is whether route origin location times change after any
timezone change, if schedules are fixed in UTC, or they depend on origin or
destination location business considerations or airport services availability.
Is there an estimated date when this change will be published?
Is there a way to get the current, most up to date version of the TZDB from
your website? We are using this one:
https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz
but it does not contain Paraguay timezone change.
You should have your own process to test changes based on the data in the tzdb
development repository, which contains all changes pending release:
https://github.com/eggert/tz
plus any changes that you may become aware of, and issues that occur during
testing.
For more information, see:
https://data.iana.org/time-zones/tz-link.html
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
