Обсуждение: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?

Поиск
Список
Период
Сортировка

[JDBC] Cut 42.1.5 now and start merging for 42.2.0?

От
Jorge Solórzano
Дата:
The Backlog of pgjdbc is getting bigger and bigger, there are many features that are ready but require review.

Should we cut 42.1.5 now and start merging for 42.2.0? or just start merging ready features and release 42.2.0 soon?

Jorge Solórzano

Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?

От
Dave Cramer
Дата:
The idea was to get people to review. How does cutting a version now help us ?




On 4 October 2017 at 13:09, Jorge Solórzano <jorsol@gmail.com> wrote:
The Backlog of pgjdbc is getting bigger and bigger, there are many features that are ready but require review.

Should we cut 42.1.5 now and start merging for 42.2.0? or just start merging ready features and release 42.2.0 soon?

Jorge Solórzano

Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?

От
Jorge Solórzano
Дата:
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.

Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?

От
Dave Cramer
Дата:
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.

Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?

От
Jorge Solórzano
Дата:
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@fastcrypt.com> wrote:
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.


Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?

От
Dave Cramer
Дата:
Hi Jorge,


sorry for the late reply. I think both Vladimir and I are just busy. I know he's at a conf in St Petersburg (or Moscow)

I don't think there is any urgency ?


On 2 November 2017 at 12:09, Jorge Solórzano <jorsol@gmail.com> wrote:
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@fastcrypt.com> wrote:
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.



Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?

От
Jorge Solórzano
Дата:
Don't worry Dave, I know both might be busy, there is no urgency.

If I can help in the review/approval process let me know.


Jorge Solórzano

On Fri, Nov 3, 2017 at 4:40 AM, Dave Cramer <pg@fastcrypt.com> wrote:
Hi Jorge,


sorry for the late reply. I think both Vladimir and I are just busy. I know he's at a conf in St Petersburg (or Moscow)

I don't think there is any urgency ?


On 2 November 2017 at 12:09, Jorge Solórzano <jorsol@gmail.com> wrote:
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órzan
​o​