From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | John Lister <john(dot)lister(at)kickstone(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Versioning - was JDBC 4 Compliance |
Date: | 2013-06-27 12:22:05 |
Message-ID: | CADK3HH+cHZ9reSPg8SPw9rNaBVt8=f5bOP3WGitZshz=e9pP0g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
John,
I'm trying to understand how changing the version number of the driver
would affect all of the current users.
There are quite a few people using the driver and suddenly moving it seems
precipitous
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On Mon, Jun 24, 2013 at 5:44 PM, John Lister <john(dot)lister(at)kickstone(dot)com>wrote:
> I mentioned it in my previous post, but what are the lists thoughts on
> using a different versioning strategy for the driver in a similar manner to
> other OS projects.
>
> My suggestion would be to:
> - freeze the current release at v1.x for partial JDBC4 support
> - archive the pre JDBC4 versions completely
> - start a new version 2, for example incorporating the major NIO and XA
> changes previously discussed running on the current JDK incorporating stubs
> or complete functions for the latest JDBC spec features as needed, etc and
> supporting the latest versions of Postgres as appropriate
>
> Work would progress with v2 with only significant bug fixes to then be
> propagated back to v1.
>
> Hopefully this reaches some compromise for the stability issues with
> existing users who can remain on v1 with newer projects migrating to the v2.
>
> At some point in the future I'd envisage a new version being released for
> example with the release of JDK8 or JDBC5 as required..
>
> John
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-jdbc<http://www.postgresql.org/mailpref/pgsql-jdbc>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Hastie | 2013-06-27 12:45:03 | Re: JDBC 4 Compliance |
Previous Message | Andreas Joseph Krogh | 2013-06-27 10:08:24 | Re: JDBC 4 Compliance |