[tz] Another change on Brazilian DST time

[Fábio Gomes]

The last DST change is already informed in Time and Date site:

https://www.timeanddate.com/time/change/brazil
https://www.timeanddate.com/news/time/brazil-delays-dst-2018.html
https://www.timeanddate.com/news/time/brazil-delays-dst-2018.html

Would this be enough to update tzdata in IANA's site?

Thanks guys
________________________________
De: Rodrigo Brüning Wessler <madigo at gmail.com>
Enviado: segunda-feira, 8 de outubro de 2018 17:15
Para: mj1856 at hotmail.com
Cc: eggert at cs.ucla.edu; flgoms at hotmail.com; tz at iana.org
Assunto: Re: [tz] Another change on Brazilian DST time

Yes, we are still waiting for the oficial presidencial decree about the DST change.
IATA and ABEAR argue that the DST change will afect 3 millon people that travel by airplane on affect period.

We had elections in Brazil yesterday, including for president. So all the attention was on that, may be this week we will have an official decision.

More two sources:
https://veja.abril.com.br/economia/companhias-aereas-reclamam-de-nova-alteracao-no-horario-de-verao/
http://agenciabrasil.ebc.com.br/economia/noticia/2018-10/aereas-dizem-que-mudanca-no-horario-de-verao-vai-prejudicar-passageiro

Em seg, 8 de out de 2018 às 16:02, Matt Johnson <mj1856 at hotmail.com<mailto:mj1856 at hotmail.com>> escreveu:
Apparently both IATA and Brazil's own airline industry (ABEAR) are pushing back on the government, citing at least three million passengers on 42 thousand flights will be affected.

Also stated by ABEAR's representative (translated via Google Translate): "Short-term changes bring risks to the entire operation of airlines".   It's good to see others have realized the risk.  I worry about the back and forth though.


https://www.panrotas.com.br/aviacao/aeroportos/2018/10/iata-ve-troca-no-horario-de-verao-com-profunda-preocupacao_159365.html

https://www.panrotas.com.br/aviacao/empresas/2018/10/abear-se-posiciona-contra-a-mudanca-do-horario-de-verao_159323.html

http://www.abear.com.br/imprensa/notas-e-releases/mostrar/posicionamento-abear-sobre-mudanca-do-horario-de-verao


-Matt



________________________________
From: tz <tz-bounces at iana.org<mailto:tz-bounces at iana.org>> on behalf of Paul Eggert <eggert at cs.ucla.edu<mailto:eggert at cs.ucla.edu>>
Sent: Thursday, October 4, 2018 8:37 AM
To: Fábio Gomes
Cc: Time Zone Mailing List
Subject: Re: [tz] Another change on Brazilian DST time

On 10/4/18 4:49 AM, Fábio Gomes wrote:
>   How long does it takes to update tzdata with this new information?


It depends on what you consider an "update". I just now updated the
development version <https://github.com/eggert/tz> with the attached
patch, and you can use that now if you like. I'd like to plan for a new
tzdb release soon after the presidential decree is published (please let
me know when that happens).


> we have a very shourt window to apply this new update.


That's unfortunately true. We have a paragraph about this in
<https://data.iana.org/time-zones/tz-link.html>. Here's how Google
Translate renders it in Portuguese, and perhaps you can improve this
translation and send it to Moreira Franco, the minister of Mines and
Energy, who's supposed to be in charge of DST in Brazil:


---


Se o seu governo planeja alterar seus limites de fuso horário ou as
regras de horário de verão, informe <tz at iana.org<mailto:tz at iana.org>> com bastante
antecedência, pois isso coordenará as atualizações para muitos telefones
celulares, computadores e outros dispositivos em todo o mundo. Com menos
de um ano de antecedência, há uma boa chance de que alguns relógios
baseados em computador operem incorretamente após a alteração, devido a
atrasos na propagação de atualizações de software e dados. Quanto mais
curto for o aviso, mais prováveis serão os problemas do relógio; veja
"Sobre o tempo das mudanças de fuso horário"
<https://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/>
para exemplos.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tz/attachments/20181009/6754f46b/attachment.html>