[tz] Policy Suggestion: Minimum time period betwen releases
Ali Al Amine
ali at towbe.com
Mon Mar 27 17:37:14 UTC 2023
The problem is that currently this database is expected to change
immediately, as well as vendors are expected to release asap (no
expectations, just asap). Having a clear, structured release timeline, and
rules that would structure such a mess, would remove the risk of such a
thing to happen in the future (or at least it would attempt to organize
it). Howard's or my suggestions are trying to setup such a structure.
@Rany Yes but that's why there should be a minimum of some sort, a minimum
that has a leeway in adding the tz database, as well as for the vendors to
update. That way all updates are synchronized as expected by the time
people go forward with the change.
@Deborah I'm from lebanon, and this is how institutions worked with it with
such a short notice:
- Banks didn't go forward with the change with international transactions
as to not have confusion with the transactions with the international banks
and their systems
- Apps that rely on cloud providers (like our case) didn't know what to
work with as the vendors cannot update on the fly. We contacted AWS for our
case as an example and what they told us is that there is no timeline for
when the update would happen, so we need to change our codebase to take
both into consideration as it might happen at any time and our code should
handle the inconsistencies that appear.
- Systems that rely on 3rd party vendors (for example quickbooks for
accounting, or any software the businesses are relying on) are reporting
everything in the wrong date as they didn't update, and they also don't
have a timeline for when the update will happen.
On Mon, Mar 27, 2023 at 8:18 PM Rany Hany via tz <tz at iana.org> wrote:
> Also I forgot to mention that most vendors have a significant delay in
> updating their tz database, which means that even if a country provides
> notice to the maintainers one month prior to a change, it will not be
> reflected on other devices in a timely manner. This makes it even more
> important to issue updates in a timely manner without delay.
> On 3/27/23 20:13, Rany Hany via tz wrote:
> > While I understand your frustration with recent chaos caused by poor
> > planning, I have to respectfully reject your proposal for the
> > following reasons:
> > Firstly, implementing a 30-day minimum period between releases would
> > punish users who have outdated tzdata solely because they are ruled by
> > incompetent governments. While it may be easy to blame politicians for
> > poor planning, citizens and businesses should not be penalized for
> > factors beyond their control.
> > Secondly, deliberately making the latest tzinfo inaccurate would only
> > lead to more issues rather than solve them. Accurate and up-to-date
> > time zone information is essential for global communication and
> > coordination, and any intentional inaccuracy would create confusion
> > and further chaos.
> > Best
> > On 3/27/23 19:46, Howard Hinnant via tz wrote:
> >> Recent events have brought to my attention the need to put a damper
> >> on chaos caused by poor planning. When governments give little
> >> notice to changes in time zone rules, this is not a problem that this
> >> group can fix, or should even try.
> >> I propose a minimum period of 30 days between successive IANA tz
> >> database releases. The train leaves the station no more frequently
> >> than once every 30 days (and will probably be less frequent).
> >> Whatever information is solid before the release date makes it on the
> >> train. Otherwise it can wait another 30 days (at least).
> >> My recommendation is in part based on this common statement:
> >> Poor planning on your part does not constitute an emergency on
> >> my part
> >> This week’s chaos isn’t unusual. In fact it is normal, especially
> >> for some countries. If they can’t be bothered to make a plan in
> >> advance and stick with it, I don’t see why this group of volunteers
> >> needs to compensate for that. Let the politicians lie in the beds
> >> they make.
> >> Howard
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tz