Re: Versioning policy PgJDBC - discussion - Mailing list pgsql-jdbc

From Jorge Solórzano
Subject Re: Versioning policy PgJDBC - discussion
Date
Msg-id CA+cVU8OrM4iFoWWfyHoouVCJRi8kSA3QkyrY0VbPHtqXHFSMSA@mail.gmail.com
Whole thread Raw
In response to Re: Versioning policy PgJDBC - discussion  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
Responses Re: Versioning policy PgJDBC - discussion
List pgsql-jdbc
In that case I only see 2 options,
a) pospone the release (actual 9.4.1213) until everything is setup to the 42 change.
or b) continue with the actual versioning, and make the change to 42 "when it's ready".

Jorge

On Mon, Nov 28, 2016 at 10:56 AM, Vladimir Sitnikov <sitnikov.vladimir@gmail.com> wrote:
>I guess there is no schedule defined to the 42.0.0 release, maybe late december, early january, or there are intentions to be early december?

Technically speaking the aim is to have a month or two between releases.
Well, current milestone has slipped a bit https://github.com/pgjdbc/pgjdbc/milestones, however there are just a couple of issues due.
https://github.com/pgjdbc/pgjdbc/pull/690 "executeBatch vs serverprepared=0" -- needs review
https://github.com/pgjdbc/pgjdbc/pull/611 "feat: allow byte[] and String to be accessed as .getLob, and .getClob" -- test should be reviewed (e.g. assert messages added)

Vladimir

pgsql-jdbc by date:

Previous
From: Vladimir Sitnikov
Date:
Subject: Re: Versioning policy PgJDBC - discussion
Next
From: Vladimir Sitnikov
Date:
Subject: Re: Versioning policy PgJDBC - discussion