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.96) (envelope-from ) id 1wDOPn-002v6D-1L for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Apr 2026 15:13:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wDOPm-0063I2-2I for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Apr 2026 15:13:58 +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.96) (envelope-from ) id 1wDOPm-0063Ht-1E for pgsql-hackers@lists.postgresql.org; Thu, 16 Apr 2026 15:13:58 +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.98.2) (envelope-from ) id 1wDOPj-00000001KVC-45px for pgsql-hackers@lists.postgresql.org; Thu, 16 Apr 2026 15:13:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; 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=+fjgeTL7ZAEj4QanvGYRcnwnjRRloLb832h6Z2rqpCQ=; b=Vi3ZN OonXWFs9070rPu4bBKWXzHQ71oxRVUe/nxjze39K2vivxkAYSiaLmUfqKqBB7nONCidqUngn+LNKj MjREM62j+5PO/b1cLcVPWwqhI2ZhCvxRCps4VKJwdWCmc0ela0i5jlJZBwDOSUdFgcUPmITxCtI9Q U10czbBX0JGr6kW2dJ05ygzNv3KT2RPAJudcRsZIiC7Mso52p/MjW1JBz+VqkI5Qd9ZJnlpvP/AbS uA+nBaoV4yxlEyGHpakV2tLrnRQJzXKb3NcIsanBdTO9robKbGgFwffgbMwkCqHSeUXmcV0v/jcRd BZI0FR3pLEUh3piu/z6AnymeioTBQ==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wDOPf-00000002hzF-2WS0; Thu, 16 Apr 2026 11:13:51 -0400 Date: Thu, 16 Apr 2026 11:13:51 -0400 From: Bruce Momjian To: Michael Banck Cc: Jacob Champion , Ashutosh Bapat , Heikki Linnakangas , PostgreSQL-development Subject: Re: First draft of PG 19 release notes Message-ID: References: <20260416075457.GA25798@p46.dedyn.io;lightning.p46.dedyn.io> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260416075457.GA25798@p46.dedyn.io;lightning.p46.dedyn.io> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Apr 16, 2026 at 09:54:57AM +0200, Michael Banck wrote: > > Well, I am guessing you didn't read this thread fully: > > > > https://www.postgresql.org/message-id/flat/adElLtegJxi6Yecv%40momjian.us > > > > This was specifically for "Co-authored-by:" == committer, but the text > > was not clear enough. However, that doesn't match your usage where a > > missing "Author" is considered to be the committer. > > I think if the committer omits an "Author" tag, but credits a > non-committer as "Co-Author", then both the committer and the > non-committer should be considered authors and credited in the release > notes. > > What would be the use-case for a sole non-committer "Co-Author" (as > opposed to just crediting the non-committer as "Author") otherwise be? I agree with you, and made that case in January of 2025 and in the email thread URL above. However, I seemed to annoy people more than help them, so I am not going to revisit it. If someone else wants to restart that thread and get a different consensus, feel free to do so. My guess is that most (vocal?) committers prefer to have Author and Co-Author indicate different levels of authorship in the commit text, rather than have them have different behavior for release note authorship. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.