[tahoe-lafs-trac-stream] [tahoe-lafs] #1077: consistent timestamp format and timezone
tahoe-lafs
trac at tahoe-lafs.org
Wed May 22 23:42:31 UTC 2013
#1077: consistent timestamp format and timezone
------------------------+------------------------------------
Reporter: zooko | Owner: zooko
Type: defect | Status: assigned
Priority: major | Milestone: soon
Component: code | Version: 1.7β
Resolution: | Keywords: time usability logging
Launchpad Bug: |
------------------------+------------------------------------
Description changed by zooko:
Old description:
> All timestamps which are visible in the user interface, log files or
> other files, automatically generated filenames, etc., should be in the
> same format and timezone. For the present, that format should be RFC 3339
> format, e.g. {{{2010-06-12 03:54:00.12345}}}. There is code in
> [source:src/allmydata/util/time_format.py at 4005#L11 time_format.py] that
> will generate this format (if you tell it to use a space char as
> separator instead of the default underscore char as separator).
>
> For the present, the timezone should be UTC. For added unambiguity,
> append the char {{{Z}}} to the end of the timestamp to indicate UTC.
>
> I'll open separate tickets to make the formatting and timezone
> localizable without losing the consistency and unambiguity. This ticket
> is just about achieving consistency and unambiguity.
New description:
All timestamps which are visible in the user interface, log files or other
files, automatically generated filenames, etc., should be in the same
format and timezone. For the present, that format should be RFC 3339
format, e.g. {{{2010-06-12 03:54:00.12345}}}. There is code in
[source:trunk/src/allmydata/util/time_format.py?annotate=blame&rev=7607268a58f31842f94c415a3403c6740c898679
time_format.py] that will generate this format (if you tell it to use a
space char as separator instead of the default underscore char as
separator).
For the present, the timezone should be UTC. For added unambiguity, append
the char {{{Z}}} to the end of the timestamp to indicate UTC.
I'll open separate tickets to make the formatting and timezone localizable
without losing the consistency and unambiguity. This ticket is just about
achieving consistency and unambiguity.
--
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1077#comment:10>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list