Feature #388
Use local time
| Status: | Closed | Start date: | 06/10/2010 | |
|---|---|---|---|---|
| Priority: | (P3) Normal | Due date: | ||
| Assignee: | Christoph Hofmann | % Done: | 100% |
|
| Category: | - | |||
| Target version: | 0.9.0-alpha2 | |||
| Severity: | Normal | |||
| Story points | - | |||
| Velocity based estimate | - |
Description
It is ok when the dSS internally use UTC time, because it is easier to handle timer events etc. But whenever the time is visible to the user (web UI, log files, ...) the user should get the local time. The timezone (and daylight savings) should be configurable via UI.
Related issues
History
Updated by Miguel Rodriguez over 1 year ago
- Status changed from New to Assigned
- Assignee set to Sergey Bostandzhyan
- Target version set to 0.9.0-alpha1
Write time zone with the time info
Updated by Miguel Rodriguez over 1 year ago
- Target version changed from 0.9.0-alpha1 to 0.9.0-alpha2
Updated by Sergey Bostandzhyan over 1 year ago
- % Done changed from 0 to 100
Time in the logs and in JSON is now printed as local time. Events can be scheduled either in local or in UTC time (depending on the ISO 8601 string). Internally the dSS keeps using UTC, conversion to local time is done only on output.
The timezone (and daylight savings) should be configurable via UI.
This is covered by #419
Merge request submitted.
Updated by Sergey Bostandzhyan over 1 year ago
- Status changed from Assigned to Resolved
- Assignee changed from Sergey Bostandzhyan to Christoph Hofmann
Merged into mainline.
One problem remains however, we still are investigating how to deal with it:
when daylight savings happen on the system or when time zone is changed while the dSS is running, the dSS will not notice this changes and needs to be restarted.
Updated by Miguel Rodriguez over 1 year ago
- Status changed from Resolved to Closed