More frequent jdbc releases are probably a good idea, but I still would
expect that they are being made from patches applied to the 7.1 branch,
not being pulled from the 7.2 main trunk. What happens when changes to
the backend for 7.2 start requiring changes to jdbc that may not be
backwardly compatible with 7.1? Isn't the whole point of having a 7.1
branch meant to have a place for patches/bug fixes that are isolated
from new feature development?
thanks,
--Barry
Bruce Momjian wrote:
>> I have JDBC2 here, and can test the compile. I am focusing on the CVS
>> because I have major jdbc patches back to February already applied.
>> There are so many fixes in CVS now, I am not sure how valuable 7.1.2
>> jdbc will be even with this one patch.
>>
>> 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.
>
>
> One more issue is that I am thinking JDBC will be similar to ODBC in
> that it will start releasing more frequently, independent of our major
> releases, Both interfaces need more frequent feedback to users.
>