Re: code contributions for 2025, WIP version

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: code contributions for 2025, WIP version
Date: 2026-04-17 14:16:35
Message-ID: h7zgaslhj3ghfy4b6hpy2vpol4ffrgjvpwwhm3253auz2telzm@gwk5lsfx5igm
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Tue, Jan 13, 2026 at 02:54:59PM -0500, Robert Haas wrote:
> Hi,
>
> A draft of my analysis of code contributions for 2025 can be found at
> https://sites.google.com/site/robertmhaas/contributions in
> contributions2025-wip.dmp. In contrast to previous years, I was able
> to do much more of this in an automated way this year: the principal
> author of the commit was computed by grabbing the first Author or
> Co-Authored-By tag from the commit message rather than by manual
> inspection of all the commit messages. Yay!

Somewhat late to the party (wanted to write right away, got distracted
for a few moments, and boom -- it's already few months old), but do you
consider gathering statistics based on Reviewed-by? It might give a
bit of appreciation for reviewing, which is commonly considered as a
thankless job, and will be more direct than just measuring amount of
emails to hackers.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Henson Choi 2026-04-17 14:24:37 Re: Row pattern recognition
Previous Message vignesh C 2026-04-17 13:55:42 Re: Fix tab completion after EXCEPT (...) in IMPORT FOREIGN SCHEMA