[tz] Notice Lead Time Tracking
tim at timtimeonline.com
Sat Jan 12 03:56:23 UTC 2019
I've put something together using GitHub Pages; the advantage being that
the metadata can stay in a machine-readable format (in this case, YAML),
while the Jekyll engine can render pretty pages and do calculations for
human consumption. (The choice of technologies is maybe not my immediate
preference, but this strikes me as most readily sustainable, by far.)
Browse the metadata at https://tzdata-meta.timtimeonline.com/
View the repository at https://github.com/timparenti/tzdata-meta
I intentionally kept the data a bit leaner, though, than Brian's original
suggestions, and have backfilled metadata through changes the tz mailing
list was first informed of since 2016-01-01T00Z. 2016 had a lot of changes
(particularly in Russia) which were going on simultaneously, which made
tracking down some of the original emails more difficult, and so there's a
bit of guesswork involved. I don't intend to go back any further than
this, nor do I particularly encourage others to do so, either.
If there are glaring omissions that keep this resource from being as useful
as it could be, I'm happy to hear it, though I am interested in keeping
this relatively lean so that it can remain fairly easily updated as new
changes to tzdata arise.
On Sun, 30 Dec 2018 at 13:26, Tim Parenti <tim at timtimeonline.com> wrote:
> I could probably whip up something basic as an early prototype for broader
> feedback. I agree that starting with notices received from 2019-01-01T00Z
> onwards is probably a reasonable cutoff for now.
> Tim Parenti
> On Sun, 30 Dec 2018 at 13:02, Philip Paeps <philip at trouble.is> wrote:
>> On 2018-12-30 10:33:29 (-0700), Brian Inglis wrote:
>> >Given some recent last minute end of year announcements
>> Not just the end of year ... I remember quite a few short- and no-notice
>> changes this year.
>> >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.
>> Excellent idea!
>> >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.
>> Starting with 2019 would be a very good start.
>> Philip Paeps
>> Senior Reality Engineer
>> Ministry of Information
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tz