Reopening this as the comments indicate misunderstanding. This bug is about displaying the timezone offset instead of the timezone abbreviation, such as defined by RFC3339 or ISO8601.
Wallclock timestamps displaying their offset are unambiguous and can be parsed and converted. Wallclock timestamps using abbreviations can refer to several points in time (as regious share abbreviations), or even two points in time in the same region if it occurred during a daylight savings time transition. It struck me as wrong that the machine readable JSON and YAML output is using a timestamp format that cannot be parsed.
Reopening this as the comments indicate misunderstanding. This bug is about displaying the timezone offset instead of the timezone abbreviation, such as defined by RFC3339 or ISO8601.
Wallclock timestamps displaying their offset are unambiguous and can be parsed and converted. Wallclock timestamps using abbreviations can refer to several points in time (as regious share abbreviations), or even two points in time in the same region if it occurred during a daylight savings time transition. It struck me as wrong that the machine readable JSON and YAML output is using a timestamp format that cannot be parsed.