public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: Dmitry Dolgov <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Date: Sun, 19 May 2024 20:20:52 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CA+TgmobnTcNq1xQE_+jxBEtj+AjKg0r_p5YNFHDE+EDnpcpFxA@mail.gmail.com>
<[email protected]>
<[email protected]>
On Sun, May 19, 2024 at 03:18:11PM -0400, Tom Lane wrote:
> * Another reason for things sitting a long time is that they're too
> big to review without an unreasonable amount of effort. We should
> encourage authors to break large patches into smaller stepwise
> refinements. It may seem like that will result in taking forever
> to reach the end goal, but dropping a huge patchset on the community
> isn't going to give speedy results either.
I think it is sometimes hard to incrementally apply patches if the
long-term goal isn't agreed or know to be achievable.
> * Before starting this thread, Robert did a lot of very valuable
> review of some individual patches. I think what prompted him to
> start the thread was the realization that he'd only made a small
> dent in the problem. Maybe we could divide and conquer: get a
> dozen-or-so senior contributors to split up the list of pending
> patches and then look at each one with an eye to what needs to
> happen to move it along (*not* to commit it right away, although
> in some cases maybe that's the thing to do). It'd be great if
> that could happen just before each commitfest, but that's probably
> not practical with the current patch volume. What I'm thinking
> for the moment is to try to make that happen once a year or so.
For me, if someone already knows what the blocker is, it saves me a lot
of time if they can state that somewhere.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
view thread (11+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox