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 1w9lUi-001j49-2J for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 15:04:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9lUg-009fD0-2P for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 15:04:03 +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 1w9lUg-009fCs-1W for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 15:04:02 +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 1w9lUe-00000000usf-1V9g for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 15:04:02 +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=ueRt4d2oNRAGT0sPMTQQAbxoy8X6i8Uipl89vZDtyAE=; b=KKYvB a7BkTekyioQd+CLvSW5VDMaJZ4oVpHzFEHxazKatwqscaMnZMBsYRkb44Fg5VXyvFAjZE1oN52pS6 ctKhx6JnZqHMRctRxfvUi4MXnXf2AHCXYa7h1EjQSeD/1NhlRENxKLJvK2e7kVPtIrHyYJ8gMwCgE MarzYB8CyYPUeJ6rzM4IuAECJE/rk0aJR9yc1Q5LQdNHRZyupHB1mZktvqSvikIBCwCeQXx4Mqh9N WH1r2JzjeoTFbwHEsD3TbaNVaHEHsvrEh4pjrmleI74Ache0zemPFA9gTdWT0Oz23f3LNV2qamHpW WQxnaiTzS5vI+W5GIuk1ZsdwQgbHQ==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w9lUb-00000002txA-1Wuo; Mon, 06 Apr 2026 11:03:57 -0400 Date: Mon, 6 Apr 2026 11:03:57 -0400 From: Bruce Momjian To: Andrew Dunstan 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> <7b16a213-7251-4bd2-add7-824ee2e8b030@dunslane.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7b16a213-7251-4bd2-add7-824ee2e8b030@dunslane.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Apr 6, 2026 at 10:56:49AM -0400, Andrew Dunstan wrote: > > On 2026-04-06 Mo 10:29 AM, 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. > > > > Possibly. I think we're tying ourselves up in knots needlessly here, though. To > me, without having to interpret the exact meaning by consulting a wiki, > Co-authored-by signifies that the person made a significant contribution, but > not as much as the Author(s). These things shouldn't be technical terms of art. > > Personally, I'm in favor of being fairly liberal about giving release note > credits. So "Co-authored-by:" shows a level of involvement, but doesn't have any effect on the major release notes. That works too. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.