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 1w9lK9-001itN-2A for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 14:53:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9lK7-009Oao-31 for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 14:53:08 +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 1w9lK7-009Oaf-25 for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 14:53:08 +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 1w9lK5-00000000ukx-2LaW for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 14:53:07 +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=MsHyoxpYlXuZRHAXZbCXsvrHxV0bptpaAvfHu9bSzYc=; b=LdXy1Cq4+tdS1WidhhuN5apPR7 JGGWW+HgsE/uxgyIGCZYivNkdb0SFwXZKkh+n9Lwk+v/VrziAKwqwe4IFTPa2Jz5I3/6D+K7rCp6i ZtYN3TfQOWAcEvfh8EGXEwWqsVnpck3EgB6qQ8vfhgfblhS9xKsse7aRoWoVBr8Bp42n//ta66DoK NEhT7FTvC8tG0KCA73PG3w7lXKCCnh7bZwfnHZUHz5giXmEJO04ykoBK5hDcX/IkHGPPvl/vDl3hJ oBwk+84jlcmnRymczdzSOm57nYVejPYrzePgW5oGjdr1e/4K88oleprD4vQ4q6DU7kqoUdOzfwRDA E1y2TtMg==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w9lK3-00000002qsr-0kUT; Mon, 06 Apr 2026 10:53:03 -0400 Date: Mon, 6 Apr 2026 10:53:03 -0400 From: Bruce Momjian To: "David G. Johnston" 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=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 07:42:52AM -0700, David G. Johnston wrote: > On Monday, April 6, 2026, Bruce Momjian wrote: > > > I think having "Co-authored-by:" mean one thing when "Author" appears > and a different thing when "Author" is missing is too confusing. > > > The community hasn’t recognized intermediate contributions between authorship > and reviewer.  Co-Author has always been available for technical reasons but > doesn’t actually convey less status than Author even if some people intended it > to be used that way.  I don’t think we should change that.  Stating it more > clearly seems warranted. Okay, I am fine with that, though it does not give committers any way to indicate via tags that they changed the patch when they don't want to be listed as author. They can just state that in the commit text. > Co-authored never means any thing different than “one of the authors”.  It’s > committed-by whose meaning changes in the presence/absence of author.  I > likewise don’t see changing that.  For future users of this information, having > a silent boundary at which the meaning/usage of labels changes is very > annoying. Uh, is this what people want, because it is at least logical and a rule that can be followed. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.