[tz] tzdata 2016g

Paul.Koning at dell.com Paul.Koning at dell.com
Mon Sep 26 20:17:50 UTC 2016

> On Sep 26, 2016, at 4:09 PM, Paul Eggert <eggert at cs.ucla.edu> wrote:
> On 09/26/2016 10:58 AM, Matt Johnson wrote:
>> Paul, could you educate us all on what the publishing process with ICANN involves?
> ICANN has a private Git-based repository that stores distribution tarballs and metadata. When I cut a new release I send them a copy of it, and they turn a crank that installs it into their private repository and then publishes the result on their web site. Although ICANN granted me access to their private system so that I could update the repository and push a button to turn the crank, the access was via Juniper VPN and was so flaky and awkward for me that I eventually gave up using it and we fell back on the current approach.

If that's all there is, then their whole task amounts to a few hundred lines of Python or some other scripting language, and the time required to publish a release should be measured in seconds.  There's nothing in what you described that appears to need any human intervention at all, let alone human intervention by humans who take weeks to do their job.


More information about the tz mailing list