Re: post-freeze damage control
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Michael Paquier <michael@paquier.xyz>,
Thomas Munro <thomas.munro@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2024-04-09T05:59:08Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
revert: Transform OR clauses to ANY expression
- ff9f72c68f67 17.0 landed
-
Fix incorrect calculation in BlockRefTableEntryGetBlocks.
- 55a5ee30cd65 17.0 cited
On 09.04.24 00:58, Michael Paquier wrote: > That's more linked to the fact that I was going silent without a > laptop for a few weeks before the end of the release cycle, and a way > to say to not count on me, while I was trying to keep my room clean to > avoid noise for others who would rush patches. It is a vacation > period for schools in Japan as the fiscal year finishes at the end of > March, while the rest of the world still studies/works, so that makes > trips much easier with areas being less busy when going abroad. If > you want to limit commit activity during this period, the answer is > simple then: require that all the committers live in Japan. Well, due to the Easter holiday being earlier this year, I adopted a similar approach: Go on vacation the last week of March and watch the rest from the pool. :) So far I feel this was better for my well-being.