You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix ACML information and timezone problem for VLDB (#1554)
* Update the journal track deadline and timezone for ACML 2026
* Support PT timezone with automatic daylight-saving adjustment
PT (US Pacific Time) is UTC-7 during daylight saving and UTC-8 otherwise,
so a single fixed offset cannot represent it. This was wrong for VLDB,
whose rolling deadlines span April through March and cross the DST
boundary — winter deadlines were off by one hour under the fixed UTC-7.
Resolve the offset per deadline date: PT picks UTC-7/UTC-8 based on
whether the date falls within US DST (2nd Sunday of March to 1st Sunday
of November). All other timezones keep their existing fixed offsets,
verified byte-identical across every value used in the dataset.
- showtable.rs: add is_us_dst/resolve_tz_offset; parse_deadline_to_rfc3339
now resolves the offset from the deadline date
- schema + README: add PT
- vldb.yml: switch to PT
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,7 @@ Description of the fields:
150
150
</tr>
151
151
<tr>
152
152
<td colspan="2"><code>timezone</code>*</td>
153
-
<td>Timezone of deadline, currently support <code>UTC-12</code> ~ <code>UTC+12</code>& <code>AoE</code></td>
153
+
<td>Timezone of deadline, currently support <code>UTC-12</code> ~ <code>UTC+12</code>, <code>AoE</code> & <code>PT</code> (US Pacific Time, auto-adjusts for daylight saving)</td>
0 commit comments