-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(timezone) Add new version of Alma-Ata Time #4487
base: main
Are you sure you want to change the base?
Conversation
Kazakhstan unified their timezone on march 1st, shifting the ALMT time to UTC+5. The idea would be to add two versions (i happily take ideas on the name) of ALMT time and bot-convert usages before that date to the version with +6.
Who'll take it uppon themself to do the bot run? |
Can we not just use stop using ALMT and start using AQTT going forward? |
Or a new Kazakh time? |
Can do once i know which name to use |
ALMT is still a valid entry in the tzinfo database, so this would depend on every editor to know we have an exception for it |
Well, PARIS (Europe/Paris) is a valid entry in tzinfo as well, doesn't mean we have support for it :D Just so we don't need to have Asia/Almaty (ALMT) support |
The thing is we already have ALMT support tho - so if someone sees the abbreviation template working, they'll think it can be used |
From the IANA tz database:
So to my understanding it was changed |
Summary
Kazakhstan unified their timezone on march 1st, shifting the ALMT time to UTC+5.
The idea would be to add two versions (i happily take ideas on the name) of ALMT time and bot-convert usages before that date to the version with +6.
How did you test this change?
Just data