> My main reason to reply here was this: You can also enable CI in your repository: https://github.com/postgres/postgres/blob/master/src/tools/c... - that's the same CI that happens for commitfest entries.

I need to get around to this...

> I find lkml style patch handling bad as well, particularly with every patchset revision getting its own thread. Very easy to loose track.

This is a good point, but if it works for the largest open-source software project in the world, I think it could work for Postgres too. I find that being able to reply inline to an email without having to copy-paste huge sections of an attachment is pretty valuable.

> One of the problems is that many of us end up preferring to spend time hacking on postgres than on development-process tooling / integration....

Completely agree, which is why I think we need to investigate migrating to a self-hosted SourceHut instance or something, so we can just use the tools that are provided by a company whose job it is to write those tools.