<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">I also agree this is a first good step. </div><div dir="auto"><br></div><div dir="auto">But I still would like to know whether data in back zone can be modified in the future when new data comes in.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Galaxy</div></div><div dir="auto"><br></div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: Howard Hinnant via tz <tz@iana.org> </div><div>Date: 2021-09-22 20:40 (GMT-05:00) </div><div>To: Guy Harris <gharris@sonic.net> </div><div>Cc: Stephen Colebourne <scolebourne@joda.org>, Time Zone Mailing List <tz@iana.org> </div><div>Subject: Re: [tz] Preparing to fork tzdb </div><div><br></div></div>On Sep 22, 2021, at 8:18 PM, Guy Harris <gharris@sonic.net> wrote:<br>> <br>> (I don't hold any of those views at all firmly. My personal preference for what to do in the short term is "put out 2021a plus fixes such as Samoa as 2021b, don't put out the results of the merger yet, and discuss this further to see which of those, if any, should be adopted as the new policy, or pick a policy that's not in the list if that's where we end up".)<br><br>Here we are firmly agreed. I sincerely hope that the TZ Coordinator will take this path.<br><br>Howard<br><br></body></html>