> On Friday 04 August 2006 15:30, Christopher Browne wrote:
>> Thanks to all those that have been putting in effort to knock the dust
>> off of the 1.2 code.
>>
>> It has been a reasonably busy week of knocking off little problems
>> here and there:
>>
>> - A fix to let 1.2 "play well" with some restructuring of #includes in
>> 8.2
>> - Added a new regression test that tests inheritance
>> - People turned up GCC to -Wall (generate *ALL* warnings), and have
>> stomped
>>   virtually all warnings
>> - Cleaning up of Makefiles
>> - Cleaning up of SGML tagging problems in documentation
>> - Added a table with extra types (inet, numeric, float, various
>> geometric
>> types) to "test1" regression test
>>
>> Darcy discovered a bug in 8.2 with domains with checks, and it appears
>> a fix should be in place forthwith; the plan seems to be that in view
>> of holidays in Canada, we'll revisit 8.2-based testing on Tuesday, and
>> see about RC3 on Wednesday.
>
> A quick run through test/* on my 8.2 dev box come up clean, I'll see about
> setting up a several hundred gig test before I leave for the day, but so
> far
> I think we are green light for an RC3.  the only outstanding issue I know
> of
> at this point in time is windows builds.

Thinking about it, Windows may be less of an issue than was thought,
although there may be some work that *ought* to be done...

The trouble Mastermind hit was that the process of building for Windows
seems underdocumented, not that we broke it recently.

My suspicion is that what's missing is some feedback as to configure
changes that need to be done on Windows.  I expect that people doing
builds on Windows have been making some changes and specifying much more
in terms of configure parameters than are needful on Unix-like systems.

That has the implication that those people will, with RC3 or any release,
need to specify those parms to do their builds.  Which in a sense isn't a
problem because they were probably going to do that (e.g. - do some minor
custom accomodations for Windows) anyway.

It would be nice for Windows builds to be handled with great cleanliness,
although in some senses, that *isn't* important because people don't
generally build software on Windows; they generally download a build (e.g.
- from what Dave Page will build :-)) and just run that.

There is doubtless some room to improve Windows building, so that it
doesn't require a lot of customization; cleaning that up may be a
post-1.2.0 thing...