CLDR made the required changes for 2026b in 48.2, which was released on
2026-03-17.

OpenJDK had incorporated 2026b by 2026-04-30:
https://bugs.openjdk.org/browse/JDK-8383645.

On Wed, 1 Jul 2026 at 21:08, Paul Eggert via tz <[email protected]> wrote:

> On 2026-06-30 11:00, Raul Delgado via tz wrote:
> > Our organization uses Workday and the vendor indicated that if iana.org
> takes care of the timezone change, their application will be fine around
> the time the clock was supposed to change.
> >
> > I am not familiar with the process but I would like to know was is the
> plan/timeline
>
> TZDB 2026b, released 2026-04-22, already has the BC change.
>
> Unfortunately it may take some time for this to percolate into Workday,
> as Workday uses Java which depends on CLDR for localization of the new
> time zone, and as I understand things CLDR doesn't plan to have
> localization fixes until mid-October. So at least localization, and
> perhaps timestamps, probably will not work until this is sorted out.
>
> I assume Java will be fixed soon after CLDR is fixed, and Workday will
> be fixed soon after that. So it'd be wise to monitor these fixes during
> October, and to take care when using Workday before October to schedule
> events after October, as today's Workday may mishandle the times of
> events scheduled after October in BC.
>
> One more thing. We plan to issue a new TZDB release soon, for a similar
> change planned for Alberta. And there quite possibly will also be
> similar changes in Northwest Territories and in Nunavik though this has
> not been legally confirmed yet. These other changes have issues similar
> to the BC change, for applications like Workday.
>

Reply via email to