The tools team has been working for many months to make the
datatracker's database become timezone aware, and we are ready to deploy
the result just after IETF 115.
This deployment will require taking the datatracker offline for 15-30
minutes while the underlying database is significantly altered.
We plan to deploy this change the afternoon of Monday November 14 around
1900 UTC.
The time (and the date) are subject to several preconditions (including
successful travel, and the continued health of everyone involved) coming
together - if they do not, we will try again at the same time on Tuesday
November 15.
This step is a necessary precondition for moving the datatracker onto
postgresql and more modern versions of Django.
For the curious:
The changes are extensive, and can be seen here:
https://github.com/ietf-tools/datatracker/compare/main...feat/tzaware
The best place to start to understand the underlying issue this
addresses is at
https://github.com/ietf-tools/datatracker/blob/feat/tzaware/ietf/utils/migrations/0002_convert_timestamps_to_utc.py
Robert Sparks
Tools Team Project Manager
_______________________________________________
IETF-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-announce
