public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: Thomas Munro <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: post-freeze damage control
Date: Tue, 9 Apr 2024 07:58:07 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+hUKGKqu1Zr46q0we0O_N1rd-YGqFkuHcLw=GN5T_Xjq7ihag@mail.gmail.com>
References: <CA+TgmoZS9zGgUyFeihqo=piuNhHEiRcYDHXMOkt40dUGx9n8Tg@mail.gmail.com>
<CA+hUKGKqu1Zr46q0we0O_N1rd-YGqFkuHcLw=GN5T_Xjq7ihag@mail.gmail.com>
On Tue, Apr 09, 2024 at 09:35:00AM +1200, Thomas Munro wrote:
> Mr Paquier this year announced his personal code freeze a few weeks
> back on social media, which seemed like an interesting idea I might
> adopt. Perhaps that is what some other people are doing without
> saying so, and perhaps the time they are using for that is the end of
> the calendar year. I might still be naturally inclined to crunch-like
> behaviour, but it wouldn't be at the same time as everyone else,
> except all the people who follow the same advice.
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.
Jokes apart, I really try to split commit effort across the year and
not rush things at the last minute. If something's not agreed upon
and commit-ready by the 15th of March, the chances that I would apply
it within the release cycle are really slim. That's a kind of
personal policy I have in place for a few years now.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, ../[email protected]/2-signature.asc)
download
view thread (11+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: post-freeze damage control
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox