All,
Believe me I appreciate all of the work
done on this.
However, my appreciation of the work
and effort does not change the legal ramifications. Nor does it lessen
the attention by the plant manager regional directors, production VPs,
the CEO and the board. I have tried to explain the process to them and
illustrate that ultimate responsibility lies with the Chilean government,
However they all get glassy eyed, when I start talking International standards.
My true frustration is with the Chilean
Ministry of Energy and the Chilean government as a whole (I love the country
and have enjoyed all of my trips there). I have expressed and requested
that my company express our displeasure with how this process works.
Thanks,
=========================================================================
Richard Gombert
Senior Technical Specialist
RDE & Q - IT - Global Manufacturing D/450D
330.796.4036
GTN: 447-4036
| Mailing address:
PO Box 3531 (200 Innovation Way)
Akron, OH 44309-3531
| Shipping address:
Goodyear Tire & Rubber Co.
Receiving D/530A, Bldg. 72
Attn: Richard Gombert, D/450D
1376 Tech Way Drive
Akron, Ohio 44306 |
Contains Confidential and/or Proprietary Information.
May Not Be Copied or Disseminated Without Express
Consent of The Goodyear Tire & Rubber Company
=========================================================================
From:
<Paul_Koning@dell.com>
To:
<wollman@csail.mit.edu>,
Cc:
tz@iana.org
Date:
03/01/2013 02:43 PM
Subject:
Re: [tz] [PATCH]
Updates for Chile 2013
Sent by:
tz-bounces@iana.org
On Mar 1, 2013, at 2:05 PM, Garrett Wollman wrote:
> <<On Fri, 1 Mar 2013 09:32:37 -0500, Andrew Paprocki <andrew@ishiboo.com>
said:
>
>> We have a production process based around IANA releases. This
process can
>> not depend on github snapshots. We need lead time to deploy a
real IANA
>> release to thousands of boxes in a safe manner. We can do testing
using
>> github, but that doesn't remove the need to get a regularly scheduled
(as
>> in "everyone knew about the Chile changes weeks ago")
update at least a
>> week in advance.
>
> I think you and several other people on this list are being a bit
too
> demanding of people who do this work without compensation in their
> spare time. If your process requires an "official"
release, then you
> need to fix your process, because the official release process is
not
> ordered around your scheduling demands.
The other point is that governments announce TZ changes with anywhere from
a year or two lead time, to negative lead time. A day or two is quite
common. So, realistically, timezone database changes, whether "official"
or prereleases, will often appear after the fact. Such things are
the fault of the respective governments, not of the TZ workers.
paul