[tz] Notice Lead Time Tracking

Brian Inglis Brian.Inglis at SystematicSw.ab.ca
Sun Dec 30 17:33:29 UTC 2018

Given some recent last minute end of year announcements, could I please suggest
creating a new document to formally track metadata about every time change
notice's lead time from 2019, as a basis for stats, info, distributor/vendor
additions and enhancements, walls of shame, etc. as this has never yet been
suggested AFAIR.
I could see vendors like Apple, Google, Microsoft, Oracle dev groups adding
columns to local copies to track their own responses, and using those to prod
government officials to do better.

The document could be a text file containing an HTML document with a table tracking:
	announcement date[/time],
	effective date[/time],
	lead time in years-months-days [hours:minutes:seconds],
	tzdb release date[/time],
	tzdb release lead time +/- in years-months-days [hours:minutes:seconds],
	whether change affects STD,
	whether change affects DST,
	number of zones impacted,
	list of zones impacted,
	comments about missing details etc.;
with dates[/times] in ISO formats (and perhaps also Unix format metadata
attributes, allowing for JS HTML text display customization and sorting by third
party users); times only specified when useful or notice is days, and times are
available and accurate.
If anyone has been doing this already, perhaps they could contribute their data;
and anyone with interest and time could backfill data from mailing list posts.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

More information about the tz mailing list