Kevin Fenzi wrote:
If I say:
2019-08-20 at 00:00UTC I think I can guess this to be the very start of
that day, perhaps?
2019-08-29 at 24:00UTC is... what? the last miliseconds of that day and
thus really right next to 2019-08-30 00:00UTC?
2019-08-29 24:00UTC = 2019-08-30 00:00UTC
The idea of the 24:00 (or 23:59 if you prefer) deadlines is that if the
deadline is given as 2019-08-29, you actually have until 2019-08-29 included
to publish your change, whereas using the 00:00 formulation means that the
exact same deadline would be listed as 2019-08-30, but 2019-08-30 is already
too late for your changes.
E.g., KDE Applications uses 23:59 UTC deadlines:
https://community.kde.org/Schedules/Applications/19.08_Release_Schedule
If I say: 2019-09-29 at 18:00UTC we all know what time I mean I
think,
or at least it's more clear than 00:00 and 24:00.
A deadline within the day is the other alternative (used, e.g., by KDE
Plasma:
https://community.kde.org/Schedules/Plasma_5 – I presume "midday
UTC" means 12:00 noon UTC), but IMHO it is more confusing than a 23:59/24:00
deadline, and for Fedora, it would actually mean a procedure change contrary
to my proposal.
For academic paper submissions, I have also seen both kinds of deadlines
(23:59/24:00 deadlines and mid-day (12:00 noon or some other arbitrary time)
deadlines), but never the confusing 00:00 deadlines used by Fedora.
Kevin Kofler