Re: Patch for jdbc ResultSet.getTimestamp()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: lockhart(at)fourpalms(dot)org
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Barry Lind <barry(at)xythos(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch for jdbc ResultSet.getTimestamp()
Date: 2001-05-17 06:06:35
Message-ID: 9837.990079595@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
>> I certainly will not be applying any jdbc stuff to 7.1.X. I was told
>> not to apply stuff during beta. I am sure not going to apply anything
>> to a minor release.

> OK, but if someone takes responsibility for the accuracy and
> effectiveness of a patch, then it should be considered for application.
> We had trouble during beta applying larger patches or patches which were
> not correct; some of which could be vetted by simple inspection.

Bruce got pounded (quite properly I thought) for applying patches
during late beta that he had not verified and indeed was not in a
position to verify. The rules need to be at least as stringent for
patches that go into a stable-release branch, since we don't normally
do much beta testing for dot-releases. But as long as someone has
adequately checked the patch, I don't think there should be a rule
against putting bug fixes into 7.1.* ...

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2001-05-17 11:42:54 Re: Patch for jdbc ResultSet.getTimestamp()
Previous Message Thomas Lockhart 2001-05-17 05:45:37 Re: Patch for jdbc ResultSet.getTimestamp()