Re: code contributions for 2024, WIP version - Mailing list pgsql-hackers

From Joe Conway
Subject Re: code contributions for 2024, WIP version
Date
Msg-id 496c7b50-7ff9-4c55-9292-bc8c9307e4d6@joeconway.com
Whole thread Raw
In response to Re: code contributions for 2024, WIP version  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: code contributions for 2024, WIP version
Re: code contributions for 2024, WIP version
List pgsql-hackers
On 12/3/24 10:44, Robert Haas wrote:
> On Tue, Dec 3, 2024 at 10:37 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>> On Tue, Dec 03, 2024 at 10:16:35AM +0900, Michael Paquier wrote:
>> > On Mon, Dec 02, 2024 at 04:10:22PM -0500, Robert Haas wrote:
>> >> Donning my asbestos underwear, I remain yours faithfully,
>> >
>> > Thanks for taking the time to compile all that.  That's really nice.
>>
>> +1, I always look forward to the blog post.
> 
> Thanks, glad it's appreciated.

It is definitely appreciated.

While I know you said "you will do you" when it comes to your annual 
blog, there are a number of similar efforts -- top of mind is the 
analysis done (as I understand it) by Daniel Gustafsson and Claire 
Giordano [1], as well as ongoing/recurring analysis done by the 
contributor committee. And there is the adjacent related discussion 
around commit messages/authors. It makes me wonder if there isn't a way 
to make all of our lives easier going forward.

[1] 

https://speakerdeck.com/clairegiordano/whats-in-a-postgres-major-release-an-analysis-of-contributions-in-the-v17-timeframe-claire-giordano-pgconf-eu-2024
-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: meson missing test dependencies
Next
From: Peter Geoghegan
Date:
Subject: Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?