Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s8qlt-00Firo-9n for pgsql-hackers@arkaria.postgresql.org; Mon, 20 May 2024 00:20:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s8qlt-00FKQR-4r for pgsql-hackers@arkaria.postgresql.org; Mon, 20 May 2024 00:20:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s8qls-00FKQ9-Qw for pgsql-hackers@lists.postgresql.org; Mon, 20 May 2024 00:20:56 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s8qlq-0012Yf-60 for pgsql-hackers@postgresql.org; Mon, 20 May 2024 00:20:55 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=IbHm+qzNJLtbvhj14bg14idlWYY4Jaluj9vuSiJP+7k=; b=VuOyJ xf/GwLQi6Rfv8OqeEjg9oMlv+3yZg62xaalA4M1YPph5cu+JOQlNq3G90bNUJ6X9ppJ25f/2SEIpy P0morTpvNHZ6zx2JsvZqy/1i9xwRYu6NTadV0xZmhRkvq0lBE9LoWKKj15PESplJBa3ZNIgMfK2ev 6vlay55X/3ry6GsFEswLI6UttrczATpg25rfwa1BFq/JIH2jG2tjXTHJBfDbmLTzYCXpm7WpHoiV1 OlCytoBp/3nT52n8RaZTEy4n400ph+tQ5zGeu3M62jwnIsA5hPQ5ddFsZi1pjL3/VJk6s20Bd0770 NQKeAOvg0/uFqMYosge0G5UtrkfCg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1s8qlo-0056Rd-2f; Sun, 19 May 2024 20:20:52 -0400 Date: Sun, 19 May 2024 20:20:52 -0400 From: Bruce Momjian To: Tom Lane Cc: Dmitry Dolgov <9erthalion6@gmail.com>, Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: commitfest.postgresql.org is no longer fit for purpose Message-ID: References: <20240519093719.sutsn2afqjs7vpft@ddolgov.remote.csb> <3238799.1716146291@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3238799.1716146291@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.