| Message ID | 20180226121919.14362-1-vkabatov@redhat.com |
|---|---|
| State | Accepted |
| Delegated to: | Daniel Axtens |
| Headers | show |
| Series | Include info about out-of-order events for timezone unification | expand |
| Context | Check | Description |
|---|---|---|
| dja/snowpatch-0_1_0 | warning | master/apply_patch Patch failed to apply |
| dja/snowpatch-0_1_0 | fail | Failed to apply to any branch |
Hi, > - | > Unify timezones used -- use UTC for both email submissions and internal > - events. > + events. Please note that this change doesn't modify already existing data > + so in case the instance's timezone is UTC+XX, events will appear out of > + order (as if they happened sooner) for XX hours in the events API feed. Thank you very much! I will apply this with your other patch - hopefully in the next couple of days. (I think I prefer s/sooner/earlier/ but I'm very happy to do this myself.) Thanks again for your contribution to Patchwork and to keeping it documented. Regards, Daniel > -- > 2.13.6
diff --git a/releasenotes/notes/unify-timezones-0f7022f0c2a371be.yaml b/releasenotes/notes/unify-timezones-0f7022f0c2a371be.yaml index 2513650..54e61a0 100644 --- a/releasenotes/notes/unify-timezones-0f7022f0c2a371be.yaml +++ b/releasenotes/notes/unify-timezones-0f7022f0c2a371be.yaml @@ -2,4 +2,6 @@ other: - | Unify timezones used -- use UTC for both email submissions and internal - events. + events. Please note that this change doesn't modify already existing data + so in case the instance's timezone is UTC+XX, events will appear out of + order (as if they happened sooner) for XX hours in the events API feed.