Update to IANA 2016e Timezone Release #359
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Any update? The DST changes affecting Cairo take effect in 3 days. |
|
I'll ping Tim on this one. Do be aware though: http://codeofmatt.com/2016/07/01/time-zone-chaos-inevitable-in-egypt/ |
|
@JohnColvin - If Egypt is your primary concern, I'd stick with 2016d for now. The Egyptian government essentially nullified the change made in 2016e. This will be corrected in 2016f when it is released. |
|
This is replaced by #360 as |
|
Thanks for the advice folks! We'll skip e and wait for f instead. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2016e was released a few hours ago, this updates the data to that version.