<div dir="ltr">That would simply shift the release burden from Paul to the tens/hundreds of others who patch everyone around the world in various OSes/platforms. We're not going to let our customers fail and see an incorrect time. The only "public" that would know about this is anyone subscribed to the mailing list.<div><div><br></div><div>-Andrew</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 24, 2016 at 10:16 PM, John Alvord <span dir="ltr"><<a href="mailto:johngrahamalvord@gmail.com" target="_blank">johngrahamalvord@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Just an onlooker... but if you changed the policy to an automatic 90 or 180 delay between notice of tz change and public release of new databases versions... that would tend to draw public attention to violations of the policy.</p><span class="HOEnZb"><font color="#888888">
<p dir="ltr">John Alvord</p></font></span><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Apr 24, 2016 12:23 PM, "Paul Eggert" <<a href="mailto:eggert@cs.ucla.edu" target="_blank">eggert@cs.ucla.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks and good work. Attached is a proposed patch to tz-link.htm to mention<br>
this topic and cite your blog post. (One nit in your post: two instances of<br>
"it's" should be "its".)<br>
</blockquote></div>
</div></div></blockquote></div><br></div>