Ok, if we go for a 6.6, then we will need to make sure the current
sources for JDBC are included in it (The stuff I have for 7.0 I've kept
separate).
I'll keep on plodding along with a "7.0" version of the driver, but I
won't commit anything until either 6.6 is out, or we decide that 7.0
would be imminent.
Peter
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, December 10, 1999 8:19 AM
To: Peter Mount
Cc: 'The Hermit Hacker'; Bruce Momjian; PostgreSQL-development
Subject: Re: [HACKERS] 6.6 release
Peter Mount <petermount@it.maidstone.gov.uk> writes:
> I'm also confused. So far, I've been working on the premise that the
> next release would be 7.0 because of the probably major additions
> expected, and that I'm hitting the JDBC driver hard to get as much of
> the 2.0 spec complete as is possible.
That was what I was thinking also, until yesterday. I think that the
proposal on the table is simply to consolidate/debug what we've already
done and push it out the door. If you've still got substantial work
left to finish JDBC 2.0, then it'd be better left for the next release.
I know I have a lot of little loose ends dangling on stuff that's
already "done", and a long list of nitty little bugs to fix, so it
makes sense to me to spend some time in fix-bugs-and-make-a-release
mode before going back into long-haul-feature-development mode.
Now, if other people don't have that feeling, maybe the idea of
a near-term release isn't so hot after all.
regards, tom lane