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 1w9Noq-001ONC-1C for pgsql-hackers@arkaria.postgresql.org; Sun, 05 Apr 2026 13:47:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9Noo-00313i-2s for pgsql-hackers@arkaria.postgresql.org; Sun, 05 Apr 2026 13:47:15 +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 1w9Noo-00313a-1o for pgsql-hackers@lists.postgresql.org; Sun, 05 Apr 2026 13:47:15 +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 1w9Nom-00000000jX1-1tGl for pgsql-hackers@lists.postgresql.org; Sun, 05 Apr 2026 13:47:14 +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=V9xJl2sDa76JbtbHf/ZJnwZCNZ0wB2wI37BBbX3kDOw=; b=gmiPa /kH5gDlKYFWjyzpeCuqG2G3DrXB9ap64NB4+SZeChTpwIsc6e1/ENlb/hrr/OA+TMZPdd6QHMZI8Y DduWEVwrop8qVBxnJd4oJZnSIniK077S9jOm4N2xnI6lFseRaOU4ev61qABl4VkNNBbuPeNsBligs CHu4qkVW486vV9ka55lNjrsSLboHb+OuMf/hXub+vQqzDijGvOSgK+JbRmtquYWbTSlY3S+HDZuud kuIheBsxzBkoyxwn3JnMbKpJXI/g6yDY7yG4p4Gm1pjjhtxLoq8cihXrKUMvyvAmtU+DIqEntGOh4 EDGPKIWCaqfqhPNvcWp6CjQacJ4Ww==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w9Nok-0000000E4Yz-1Kod; Sun, 05 Apr 2026 09:47:10 -0400 Date: Sun, 5 Apr 2026 09:47:10 -0400 From: Bruce Momjian To: Peter Geoghegan Cc: Andrey Borodin , PostgreSQL-development Subject: Re: PG 19 release notes and authors Message-ID: References: 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 Sat, Apr 4, 2026 at 10:12:57PM -0400, Bruce Momjian wrote: > What confuses me are cases where Authors are not the committer and > Co-authored-by are not the committer. This combination is not > documented in the wiki, which makes me think people are using > Co-authored-by in ways that are inconsistent or I don't understand. I now realize I was treating non-committers listed as Co-authored-by the same as committers being listed. Someone who is listed as Co-authored-by made changes to the patch, perhaps adding bugs, but not someone who should be listed as an author of the release note item. 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 am not sure PG 19 follows this, but we might want to follow it going forward. A larger issue is that since we now have links to the commits in the release notes, there might no longer be a need to list _any_ names next to the release note items. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.