Aside, I hope the new official version goes live around Feb. 15 in the worst case; so downstream providers (and developers) can test this new time zone without being in a hurry

Since this involves a new time zone, and thus requires changes in other databases (localization, time zone polygons), the lead time needs to be longer than usual. Now that the change is finalized, please release this. Work on the other databases is stalled until that happens.

Distributing an intermediate version from the GitHub repository is problematic because calling it either 2016j or 2017a are both incorrect. Downstream providers would have to make up an identifier which wouldn’t be cross-platform, and could cause problems with software that wasn’t expecting it.

Debbie

On Jan 19, 2017, at 8:28 PM, Juan Correa <pottersys@gmail.com> wrote:

On Fri, Jan 20, 2017, Paul Eggert <eggert@cs.ucla.edu> wrote:
If we interpret the decree modification as written, Magallanes is scheduled to change from -03 to -04 on 2019-05-11 at 24:00, which will be one hour after Santiago is scheduled to change from -03 to -04. Surely this is not intended. For now, it's simpler to assume the change will be permanent

Both Magallanes and Santiago will be on UTC -03 for this 2019 scheduled transition (Santiago shall start DST [-04 to -03] on Aug 11, 2018); so they will jump back to -04 simultaneously *if they don't change this again* (and it will jump to "hora oficial" [Santiago] nevertheless that day)

I tested the patch, and it works OK for this year. 

Aside, I hope the new official version goes live around Feb. 15 in the worst case; so downstream providers (and developers) can test this new time zone without being in a hurry

--
Juan Correa Poblete
PS Labs (http://www.pslabs.cl)