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

From Tom Kincaid
Subject Re: code contributions for 2024, WIP version
Date
Msg-id CAKPRjUNOmdpF8NDLbSAysTvZcDZ8Hi5DJab2AjpxPU6uLB1D6A@mail.gmail.com
Whole thread Raw
In response to Re: code contributions for 2024, WIP version  (Joe Conway <mail@joeconway.com>)
Responses Re: code contributions for 2024, WIP version
List pgsql-hackers



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.

Perhaps slightly off topic, so how does one provide input to the contributor committee?
 

[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




--
Thomas John Kincaid

pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: Memory leak in WAL sender with pgoutput (v10~)
Next
From: Andres Freund
Date:
Subject: Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?