From: | Sehrope Sarkuni <sehrope(at)jackdb(dot)com> |
---|---|
To: | Robert Zenz <robert(dot)zenz(at)sibvisions(dot)com> |
Cc: | "pgsql-jdbc(at)lists(dot)postgresql(dot)org" <pgsql-jdbc(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Reviewers needed for pgjdbc pull requests |
Date: | 2018-05-15 14:27:31 |
Message-ID: | CAH7T-aodMDdy0_WmH4J7JHXQXPE79Re94vBc3maxCDWKz2UJ9A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Tue, May 15, 2018 at 10:04 AM, Robert Zenz <robert(dot)zenz(at)sibvisions(dot)com>
wrote:
> I believe people (myself included) are simply not aware that them
> reviewing pull
> requests would do any good. By definition, pull requests must be reviewed
> and
> can only be merged by these which have the authority to do so. So it seems
> superfluous when somebody like me adds a "looks good to me" comment under
> a PR.
> It has to be checked by the merging person anyway.
>
It's still helpful though. Even simply chiming in to say that a particular
feature may be useful without actually reviewing a PR is helpful as it
identifies the PRs that reviewers should be focusing on (i.e. stuff that
people actually want and will use).
It works in reverse as well. New features mean new code complexity that
needs to be maintained over time. Chiming in to say that a feature makes no
sense, doesn't cover a edge cases, or that you simply would never use it
helps decide if a given change will be worth it in the long run.
-S
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Sitnikov | 2018-05-15 14:45:23 | Re: Reviewers needed for pgjdbc pull requests |
Previous Message | Sehrope Sarkuni | 2018-05-15 14:22:16 | Re: Reviewers needed for pgjdbc pull requests |