Re: Three weeks left until feature freeze

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, Kris Jurka <books(at)ejurka(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Dave Cramer <pg(at)fastcrypt(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Thomas Hallgren <thomas(at)tada(dot)se>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Three weeks left until feature freeze
Date: 2006-07-14 02:04:32
Message-ID: 44B6FBB0.4010800@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marc G. Fournier wrote:
> On Thu, 13 Jul 2006, Andrew Dunstan wrote:
>
>> Marc G. Fournier wrote:
>>>
>>> Second, its assuming that Thomas, or any other pl/java developer,
>>> *isn't* going to watching for any changes to the API fairly closely,
>>> considering they know it does happen, and, therefore, won't make a
>>> change to their development code to accommodate that when the time
>>> comes ...
>>>
>> As we have explained before, there really isn't an API in any
>> meaningful sense. Thomas will undoubtedly be vigilant, but the real
>> danger is that something non-obvious will change and break stuff.
>
> But, as Tom has already explained, *he's* not going to make changes
> pl/java if its committed ... how many will even have java (or gcj) to
> even test it to see if its broken?
>
Quite so. That's why buildfarm for pl/java will be important when I can
get it done.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kris Jurka 2006-07-14 02:06:23 include compile problems
Previous Message Marc G. Fournier 2006-07-14 01:52:46 Re: Three weeks left until feature freeze