Re: Cut 42.1.5 now and start merging for 42.2.0?

From: Jorge Solórzano <jorsol(at)gmail(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Cut 42.1.5 now and start merging for 42.2.0?
Date: 2017-10-05 13:39:17
Message-ID: CA+cVU8Mapu=x_hy2Ex9kiLcBUuJyGj56C_L6M--k_6dwjhmGwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Wed, Oct 4, 2017 at 8:34 PM, Dave Cramer <pg(at)fastcrypt(dot)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.

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2017-10-05 18:48:47 [pgjdbc/pgjdbc] ad47ab: Update thread safety status of the driver to refle...
Previous Message Dave Cramer 2017-10-05 02:34:57 Re: Cut 42.1.5 now and start merging for 42.2.0?