User tests: Successful: Unsuccessful:
Pull Request for Issue #22629
Y-m-d H:i:s T
format versus one that is translated so the format does not change based on who exports the dataTimestamp is clear as it relates to timezones and consistently formatted
Timestamp is ambiguous and can be formatted differently based on the admin who exports the logs
Status | New | ⇒ | Pending |
Category | ⇒ | Administration |
Labels |
Added:
?
|
can the GMT be changed to UTC in the file name too ?
Done.
I have tested this item
I have tested this item
use the Y-m-d H:i:s T
would not be better to use one of standard format, ISOxxx/RFCxxx/atom ?
if talk about standards
I think Y-m-d H:i:s T
is more user-friendly than a standard ISO8601 format which would make the date/time
2018-10-21T12:22:03+00:00
Plus (and I generalize here, sorry USA) most Americans would know their timezone, but not its offset to UTC/GMT.
Personally I don't think we even need the seconds in the file name but as a developer seeing H:i
without s
just looks odd :)
okay, I just asked :)
Status | Pending | ⇒ | Ready to Commit |
RTC
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-10-23 19:46:01 |
Closed_By | ⇒ | mbabker | |
Labels |
Added:
?
|
GMT !== UTC
can the GMT be changed to UTC in the file name too ?