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 1w9lN7-001iwW-0G for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 14:56:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9lN5-009WQi-1b for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 14:56:11 +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 1w9lMK-009Rjz-3A for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 14:55:25 +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 1w9lMJ-00000000ruq-21iA for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 14:55:24 +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=yeSuvY2NUnebsjCaaeROuw3BTsE19hL0RDLs4Kitfiw=; b=0+BsU M7gRVJfBQINBDBz6UagPtv+ysUOnsdPj9bbGYzHzmhUeMFBeSDmeQx9y+EEdr2KbS5ovR/3v175Fw azft5JADafUn8xXuAq1XSnj+7SEWIgw42ogkpKpcpFWgcB3gocb/XTlXhZAILy2nzJYme9i/0UYoq PYxiJHiK/RRK5Xa4Jgq/WDnijjm1bIDoM+wRZsyhm2ffCpnBXDM5dSZK5Ku0BUW0xePvaUPHw9por mbgS+HtePX0ZggjuFIsXz1rkEne3v59io2YwQzImjv4DjJbcs3bRRYS7s2Bbpq8GABb8HWvetSCME JoyiHBaHygjSdTqO2EvYsiWyrxyCg==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w9lMI-00000002r4D-2wxx; Mon, 06 Apr 2026 10:55:22 -0400 Date: Mon, 6 Apr 2026 10:55:22 -0400 From: Bruce Momjian To: John Naylor Cc: Tom Lane , Andres Freund , =?utf-8?Q?=C3=81lvaro?= Herrera , Peter Geoghegan , Andrey Borodin , PostgreSQL-development Subject: Re: PG 19 release notes and authors Message-ID: References: <202604051405.sxedzcgzky3n@alvherre.pgsql> <582789.1775401852@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Apr 6, 2026 at 09:47:32PM +0700, John Naylor wrote: > > I think having "Co-authored-by:" mean one thing when "Author" appears > > and a different thing when "Author" is missing is too confusing. > > My take is that the co-author tag has backfired and made things less > clear. If we are using it inconsistently, then it doesn't convey any > useful information. I'd actually rather just use "Author" exclusively > and if there is some further detail that needs to be conveyed, it can > be in the message body. The original intent as I understood it was for "Co-authored-by:" to be lesser authors, typically the committer, but as you said, we haven't done that consistently in the past. Do we want to do it consistently going forward or just not use "Co-authored-by:"? -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.