| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Jorge Solórzano <jorsol(at)gmail(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 19:15:21 |
| Message-ID: | CADK3HHJEYhGY4XZbpToajf+PFP1r+WTTma+heBXCkc0CANXa_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Fair enough I"ll look at the PR's you have approved.
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
On 5 October 2017 at 09:39, Jorge Solórzano <jorsol(at)gmail(dot)com> wrote:
> 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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jorge Solorzano | 2017-10-05 20:57:45 | [pgjdbc/pgjdbc] ed0a39: chore: streamlining jobs (#959) |
| Previous Message | Dave Cramer | 2017-10-05 18:48:47 | [pgjdbc/pgjdbc] ad47ab: Update thread safety status of the driver to refle... |