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 1w9n1B-001kSj-1L for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 16:41:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9n18-00ARMW-2X for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 16:41:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w9n18-00ARMO-1f for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 16:41:38 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w9n16-00000000ve4-1E4Q for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 16:41:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=nJnWXr8xzYCj0Nx7+e3etXPsE5qVjS+QkleTOmipinM=; b=a8sL9+iPeVitveF5buR4a2IKVI Jx/uAz2s6dAt6Fs6ALVNOnk91kicJ7b84Y685Lkdc38f24C35sgR6bP24nPPZYciRFLzAvqyxx9wg hNhAlnrjHnNXTMcUxNUV7WF0DO6RIdrFf4g/uff1ENvM5U/tvu4G40sqrLBkkBGT5WoGVR7RlfTc2 fKA6cut1JA3OaoeQroyAgiIrunL3V4uqnIZqGJJgAO/hcer+vY8iWZcRyVFfcnXHqQTzrr8xwsDEo xf6Z0vv+in7wC4zdWhGeEjb83d1XhKS9x8H5vg2jxAEiYRmJK0z0yx7bdOq6/v0HgNipM+1N8o/bQ V7f+GNVg==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w9n14-00000003B6J-0sEc; Mon, 06 Apr 2026 12:41:34 -0400 Date: Mon, 6 Apr 2026 12:41:34 -0400 From: Bruce Momjian To: Robert Haas Cc: 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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 11:38:41AM -0400, Robert Haas wrote: > On Sun, Apr 5, 2026 at 10:51 AM Andres Freund wrote: > > On 2026-04-05 16:09:57 +0200, Álvaro Herrera wrote: > > > On 2026-Apr-05, Bruce Momjian wrote: > > > > I just updated the wiki to handle this case because obviously > > > > Co-authored-by is listing more than just committers: > > > > > > > > https://wiki.postgresql.org/wiki/Commit_Message_Guidance#Tags%3A_%22%3A%22 > > > > Used to indicate the patch authors. "Co-authored-by:" should list > > > > individuals who modified the patch but should not be listed as > > > > authors in the release notes. > > > > I think that is a completely unwarranted change for which there is zero > > concensus. > > +1. This whole discussion is crazy to me. Every Author and Co-Author > should be listed in the release notes. If there is no author or > co-author named in the commit message, then the committer should be > listed as the sole author; otherwise, the exact list of authors and > co-authors that the committer chose to include in the commit message > should be credited. This wiki update should never have happened, and > should be reverted immediately. I don't even understand why we're > talking about this. You've invented a distinction between Author and > Co-authored-by that not a single committer seems to have ever > intended. It's just a way to indicate that some people did more work > than others, not that the co-authors do not have an authorship > interest. If they weren't supposed to be listed as authors, they would > have been listed as Reviewed-by or not at all. Uh, the original wiki text is from a discussion on pgsql-private-committers@lists.postgresql.org with subject "determining the primary author of a commit" that happened around November 2024 to March 2025. Unfortunatly there is no public archive of that discussion. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.