On 2026-11-03 14:40, Paul Eggert via tz wrote:
On 2026-11-03 12:12, Brian Inglis via tz wrote:
You should be using *version*, as it seems to be set (sometimes much) later
than NEWS, with other files modified after NEWS, but always before version:
Although 'version' is a good choice, I'm not sure where that "sometimes much"
comes from.
Until 2012g there was no consistent last updated file;
from 2012g-2014f Makefile was consistently the last updated file:
2012-10-17 21:59:46-0600 tzdata2012g/Makefile
...
2014-08-05 18:46:54-0600 tzdata2014f/Makefile
from 2014g until 2016f, Makefile and NEWS were consistently last updated files:
2014-08-28 13:32:04-0600 tzdata2014g/NEWS
2014-08-28 13:32:04-0600 tzdata2014g/Makefile
...
2016-07-05 08:29:06-0600 tzdata2016f/NEWS
2016-07-05 08:29:06-0600 tzdata2016f/Makefile
in 2016g, NEWS was last updated file:
2016-09-05 21:47:42-0600 tzdata2016g/Makefile
2016-09-13 09:59:04-0600 tzdata2016g/NEWS
from 2016h until 2020d, NEWS and version were consistently last updated files:
2016-10-20 00:19:52-0600 tzdata2016h/version
2016-10-20 00:19:52-0600 tzdata2016h/NEWS
...
2020-10-21 12:25:03-0600 tzdata2020d/version
2020-10-21 12:25:03-0600 tzdata2020d/NEWS
from 2020e until 2025a, version was consistently last updated file:
2020-12-22 16:15:43-0700 tzdata2020e/NEWS
2020-12-22 16:15:44-0700 tzdata2020e/version
...
2025-01-15 03:48:56-0700 tzdata2025a/NEWS
2025-01-15 03:48:57-0700 tzdata2025a/version
in 2025b, version was last updated, much later than NEWS:
2025-03-22 07:42:24-0600 tzdata2025b/NEWS
2025-03-22 10:11:53-0600 tzdata2025b/southamerica
2025-03-22 10:11:54-0600 tzdata2025b/version
from 2025c, version was consistently last updated file:
2025-12-10 15:43:55-0700 tzdata2025c/NEWS
2025-12-10 15:43:56-0700 tzdata2025c/version
...
2026-10-28 00:18:08-0600 tzdata2026f/NEWS
2026-10-28 00:18:09-0600 tzdata2026f/version
Makefile was (possibly joint) latest from 2012g thru 2016f;
NEWS was (possibly joint) latest from 2014g thru 2020d;
version was (possibly joint) latest from 2016h thru 2026f.
In the full-release tarball (e.g., tzdb-2026f.tar.lz), tzdata.zi is the newest
file by one second, as it depends on 'version'. Subset-release tarballs (e.g.,
tzcode2026f.tar.gz or tzdata2026f.tar.gz) lack tzdata.zi, so 'version' is the
newest file by one second; typically it is one second newer than 'NEWS' because
'NEWS' is typically the last file we hand-edit before cutting a release.
The "one second" business is implemented via the Makefile's SET_TIMESTAMP_DEP
and set-timestamps.out.
That has been consistent since 2020e, including 2025b incremented from
southamerica, updated ~2.5hours after NEWS.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry