Magnus Hagander wrote:
> On Tue, Apr 13, 2010 at 9:00 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
>> Tom Lane wrote:
>>> Alvaro Herrera <alvherre@commandprompt.com> writes:
>>>> Magnus Hagander wrote:
>>>>> This script should probably live in CVS, and be run when Microsoft
>>>>> releases new timezone data. Where should I put it - src/timezone or
>>>>> somewhere in src/tools? (it does read pgtz.c in the current directory,
>>>>> but it doesn't actually edit the file - just outputs on stdout a list
>>>>> of changes to be made to the file manually)
>>>> I think it should live in src/tools and be mentioned in
>>>> src/tools/RELEASE_CHANGES
>>> +1 for src/tools/, but the documentation note should probably be in
>>> src/timezone/README. This task isn't especially coupled to release
>>> times (at least not *our* release times). And it's definitely not
>>> likely to happen at the times anyone would be consulting
>>> RELEASE_CHANGES, because none of the release leadup work gets done
>>> on Windows machines.
>> True, but if there's a www.microsoft.com URL that could be checked for
>> timezone updates, perhaps we don't need a Windows machine. In any case,
>
> Funny guy. There isn't, of course.
>
>> perhaps whoever does the release work can *ask* someone else to provide
>> the Windows TZ patch.
>
> Yeah, that's what we'll need done.
>
> How about we put it in RELEASE_CHANGES for major releases with
> something like "if a major windows update has been released, run ...
> "?
is this really just relevant for major releases or is there a chance
that MS adds stuff like that in patches or servicepacks as well?
Stefan
