<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>If the zones are volatile, wouldn't it make more sense for someone in the Antarctic scientific community to maintain a private distribution for Antarctica?<div><br>tzdb could pull from it periodically, such as before each otherwise-scheduled release. But I'd be disappointed if a short-notice Antarctic zone change forced a new public tzdb version. For example, it's not quite the same scenario as the recent Turkey update.<br><br><div>> From: kre@munnari.OZ.AU<br>> To: Michael.Chinn@aad.gov.au<br>> Date: Fri, 30 Oct 2015 12:31:43 +0700<br>> CC: tz@iana.org<br>> Subject: Re: [tz] timezone change for antarctica\casey [SEC=UNCLASSIFIED]<br>> <br>> Date: Fri, 30 Oct 2015 05:01:39 +0000<br>> From: Michael Chinn <Michael.Chinn@aad.gov.au><br>> Message-ID: <b269372e88e94074996dbfd2b611cec1@KGS-EX02.AAD.GOV.AU><br>> <br>> | The TZ changes, particularly at Casey, are highly variable,<br>> <br>> Oh.<br>> <br>> | they are based around resupply and flights.<br>> <br>> I assume in that case that someone plans them in advance ... given the<br>> logistics, probably a fair time (months?) in advance ?<br>> <br>> | I will endeavour to go through the database and pull out the TZ changes,<br>> | should be able to get 3-4 years.<br>> <br>> Ideally we're looking to go back to at least 1970 (or whenever it was<br>> established, if more recent than that) - and even earlier if applicable<br>> and possible.<br>> <br>> But it does not have to be all at once.<br>> <br>> | Regarding predictions, sometimes there are only a couple of days<br>> | notice on changes much to the anguish of a few wintering expiditioners.<br>> <br>> Oh.<br>> <br>> | All changes are visible live on the external site (it's the same database)<br>> <br>> That just tells us the current time, and so, unless continually monitored<br>> (which I doubt anyone here really has the resources to do) isn't suitable<br>> for much more than verifying (or not) that the current data is correct, and<br>> at best, would only ever tell us that we should have changed the zone already.<br>> <br>> To be really useful, we need to know (however far in advance is possible)<br>> when the next change is coming, before it occurs. Ideally more than 2 days!<br>> <br>> kre<br>> <br></div></div> </div></body>
</html>