I believe the implication of Paul’s message is that, to help, you could test the version of tzdata currently available to you in the github repository.  He says this is likely the “final version”, so of course, if your testing shows any problems, it is better to do it now rather than after it is released.  If it does not show any problems, then perhaps you can use it in production even before the official release is made.

 

Regards,

    Malcolm

 

 

Agreed.

Please let us know if we can help.

I have a standard outage window this weekend to apply the update.

If we don't make that I have to arrange for an emergency change and a plant wide shutdown to update the dozen or so plant floor systems.

Yes the OS update does not usually require a reboot, but the application that run on those OS's do. So we have to shutdown the whole plant. Major headache for me.

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:        Deborah Goldsmith <goldsmit@apple.com>
To:        Paul Eggert <eggert@cs.ucla.edu>,
Cc:        Time Zone Database discussion <tz@iana.org>, Robert Elz <kre@munnari.oz.au>
Date:        02/28/2013 04:53 PM
Subject:        Re: [tz] [PATCH] Updates for Chile 2013
Sent by:        tz-bounces@iana.org

Hi,

Is there anything any of us can do to assist in this?

Thanks,
Deborah

On Feb 26, 2013, at 12:55 PM, Paul Eggert <eggert@CS.UCLA.EDU> wrote:

> The new version should be available soon.  In the meantime your
> folks can test with what's on github, as that's likely going
> to be the final version, except that the version number will be
> updated to 2013a.
>
> To be honest one holdup at this point is the hassle of
> jumping through all the internal security hoops to
> create an official release.  It's an unpleasant process and
> I dread having to do it.  There is some benefit to not
> being hasty, I suppose.