Postgres Pro
Downloads
Home   >   mailing lists

Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0? - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?
Date
Msg-id CADK3HHJEYhGY4XZbpToajf+PFP1r+WTTma+heBXCkc0CANXa_w@mail.gmail.com
Whole thread Raw
In response to Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?  (Jorge Solórzano <jorsol@gmail.com>)
Responses Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?  (Jorge Solórzano <jorsol@gmail.com>)
List pgsql-jdbc
Tree view
Fair enough I"ll look at the PR's you have approved.


On 5 October 2017 at 09:39, Jorge Solórzano <jorsol@gmail.com> wrote:
On Wed, Oct 4, 2017 at 8:34 PM, Dave Cramer <pg@fastcrypt.com> wrote:
The idea was to get people to review. How does cutting a version now help us ?


​Some PRs are waiting for 42.2.0​, so I suppose that cut 42.1.5 now and start merging those features for 42.2.0 makes sense...

If there will be no 42.1.5, then why have many PRs on hold?

Waiting to get people to review is not an option since there are PRs that for months haven't received any input. And the ultimate decision is on the maintainers, I have personally reviewed some PRs and give my approval but the PRs are still on hold.

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: [JDBC] [pgjdbc/pgjdbc] ad47ab: Update thread safety status of the driver torefle...
Next
From: Jorge Solorzano
Date:
Subject: [JDBC] [pgjdbc/pgjdbc] ed0a39: chore: streamlining jobs (#959)