Re: code contributions for 2024, WIP version

From: Tom Kincaid <tomjohnkincaid(at)gmail(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Christoph Berg <myon(at)debian(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Claire Giordano <Claire(dot)Giordano(at)microsoft(dot)com>
Subject: Re: code contributions for 2024, WIP version
Date: 2024-12-05 15:39:38
Message-ID: CAKPRjUNOmdpF8NDLbSAysTvZcDZ8Hi5DJab2AjpxPU6uLB1D6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2024-12-05 15:41:42 Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?
Previous Message Euler Taveira 2024-12-05 15:39:26 Re: Memory leak in WAL sender with pgoutput (v10~)