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-11-02 16:09:23 |
Message-ID: | CA+cVU8OgZoEK7SVMyiKgMfrZpLEooF0n8ZLyRKKBMgNsWnEyjQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi Dave, the merging (review) of PRs has been a bit slow, is there anything
that I can do, to make the process faster?
Jorge Solórzano
On Thu, Oct 5, 2017 at 1:15 PM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
> 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 | Dave Cramer | 2017-11-03 10:40:01 | Re: Cut 42.1.5 now and start merging for 42.2.0? |
Previous Message | Simon Riggs | 2017-11-02 08:44:44 | Re: Statement-level rollback |