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 1w9AVN-001Ec2-2n for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Apr 2026 23:34:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9AVL-000opt-3A for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Apr 2026 23:34:16 +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 1w9AVL-000opk-2E for pgsql-hackers@lists.postgresql.org; Sat, 04 Apr 2026 23:34:16 +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 1w9AVK-00000000axm-0e0f for pgsql-hackers@lists.postgresql.org; Sat, 04 Apr 2026 23:34:15 +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=cAucKtw7h8PEpkIWyiyC/nxeglZdldy+j64pbWXm2qc=; b=lxSKG JdsrQ1dHRc/3aFupDI4hZHTCAPjIjR44l7YCesCzQdmYOZMN+bhwWpaXWH2rLFCfo2IoXpd+B8+dP KhLKiTGxC/6ji2jJJFW5QIgOZpLoeCiFCLSVQdF5PAQeEkCwvR9vyRZiH4rZiLM4JGXRYmJaVAM9O L+nODt/d4E1bFQqXw67M5Np6G26I3dRAQ0a54ZqufD4nPtZ8B3jb3ZGM/ZJNUWfzVwLHlJjBkXpvk D02cLujGSHsUR8EiFLiW3+iRdBYIsTlbXKHxKjenxqyeZ8VSUGPt8XWgdOwrvMjEvEzN0I9NNtbDl NOGw1wQa16Q9I490FX+DzS7pr1FhQ==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w9AVJ-000000098Gx-0NSp; Sat, 04 Apr 2026 19:34:13 -0400 Date: Sat, 4 Apr 2026 19:34:13 -0400 From: Bruce Momjian To: Andres Freund Cc: pgsql-hackers@lists.postgresql.org, Peter Eisentraut , Matthias van de Meent Subject: Re: PG 19 release notes and authors Message-ID: References: <5047DBF5-DE47-487A-9955-3A8BA4F26F83@anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5047DBF5-DE47-487A-9955-3A8BA4F26F83@anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Apr 4, 2026 at 06:16:10PM -0400, Andres Freund wrote: > Hi, > > On April 4, 2026 5:56:01 PM EDT, Peter Eisentraut wrote: > >On 04.04.26 17:06, Matthias van de Meent wrote: > >> On Sat, 4 Apr 2026 at 16:50, Bruce Momjian wrote: > >>> > >>> In the PG 19 commits, I am seeing several commits with Author and > >>> Co-authored-by tags. FYI, I think we agreed that only the Author names > >>> are mentioned as the authors in the release notes. > >> > >> If it's not the "Co-authored-by" tag, how else would a project of a > >> non-committer cooperating with a committer be tagged? > > > >Two Author tags. > > That's not how I understood its use so far, and I'm surely not alone in that. We could rephrase this in the wiki page, but we can't go back and edit the commit messages... The wiki page says: https://wiki.postgresql.org/wiki/Commit_Message_Guidance Author: Co-authored-by: Used to indicate the patch authors. "Co-authored-by:" is used by committers when they want to give full credit to the named individuals, but also indicate that they made significant changes. but I am seeing many cases where there is an Author tag, who is not the committer, and also Co-authored-by tags in the same message. That does not follow the wiki text. I need to know what to do for PG 19, and what to do for later major releases. I think Peter's point is why are people using Author and Co-authored-by in the same commits, and not just two Authors. I thought we had this resolved but looking at the PG 19 commits, obviously not. To clarify, I assume Co-authored-by would appear in the Acknowledgments section at the bottom of the major release notes, e.g.: https://www.postgresql.org/docs/current/release-18.html#RELEASE-18-ACKNOWLEDGEMENTS -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.