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 1w9ncN-001l70-1j for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 17:20:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9ncM-00Aner-0R for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 17:20:06 +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 1w9ncL-00Anei-2j for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 17:20:06 +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 1w9ncJ-00000000vzt-2MUb for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 17:20:05 +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=Z6Aoe2CeI/ExBp2uhYK3iqA02rcBzaPVin4sMHnS1f4=; b=p6FJ9p7U5UrkiAJxtFl8jMwTTc APpHGO4Bte5oo9+UDsbioAp/sd8lzh6TUde7e+bETjMjFzi6kjjO3/+5eWpiyB+CyoGNnqnmAJzcJ mVwPf4UpsC6ucoRUTiX4aUqDWT6cHE7JDFO14uyqiNKYYRJUscaSXcjsrA+4tLn6Y6FdgL6MhC36H oD+AbHhfN3xSMWcpSVls0oI+pyDzzxkmly+6Ud9+ysSDalwlgO86JonVg9MaymuH1nwtPmwuge0vv 6GaiCHaRUczJ6PE6Ac6UxAl1GjX/4V7tuug8MBRIHK6luHWNa8QD49UAIVCm1aFL7ozn4m0XDHfp7 qBz0zd2w==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w9ncG-00000003JxB-3tYV; Mon, 06 Apr 2026 13:20:00 -0400 Date: Mon, 6 Apr 2026 13:20:00 -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 01:05:18PM -0400, Robert Haas wrote: > On Mon, Apr 6, 2026 at 12:41 PM Bruce Momjian wrote: > > 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. > > Sure, but many committers who were part of that discussion have > commented on this thread, and all of them except for you seem to agree > on what should happen here, as do all of the people who have commented > who were not party to that discussion. If you had started out this > conversation by saying "when there are both Author and Co-authored-by > tags, how am I supposed to credit that in the release notes?" and > accepted the answer you got back, I don't think anybody would be > annoyed. But now you're getting frustrated responses from a bunch of > people because you keep insisting that it must be everyone else who is > mistaken: you keep suggesting that I (and all the other committers who > have commented) misunderstood the earlier thread and the rules for > commit messages, rather than concluding that you might have been the > one who misunderstood. I am frustrated because I thought we had a rule agreed upon in January 2025, and now I am told I was wrong. At the time, some committers did say they wanted my interpretation, and I want to honor them in trying to stand up for their old messages in this thread. Personally, I don't care what the rules are. What I don't want to do is to religitate this again, and usually if we ignore what people said in the past, they will show up at some later time to try to undo what we are doing now. > It is fair to say that you need to know what the rules are, but I > really don't understand how it could be any more clear at this point > what people expect to have happen. I am confused how this was not clear in the January 2025 discussion and why people didn't mention they didn't like it then. I can't quote anything from anyone but myself from a private email, so here is some text by me to you: I started using Co-Author as a way to indicate that the Co-Author wrote some of the patch, but I modified it enough that I don't want to attribute/blame the work entirely on the Co-Author. Are you saying when that happens, I should name myself also as a Co-Author? I am now thinking it is the wiki page text that was unclear because it makes no mention of the release notes, which is why no one complained at the time. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.