git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Releasing versions on Fridays, was Re: Git Bug Report: git add --patch > "e" makes keyboard unresponsive
Date: Wed, 26 Mar 2025 08:02:22 +0100 (CET)	[thread overview]
Message-ID: <c4753c0d-d957-c4d0-a452-1e592cade34f@gmx.de> (raw)
In-Reply-To: <xmqqsen1mj1y.fsf@gitster.g>

Hi Junio,

On Tue, 25 Mar 2025, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > I have stated my preferences previously, even attempted to coordinate
> > between Git and Git for Windows, and I observe that the way I present
> > arguments is ineffective. Therefore I will try something new: Refer you to
> > a couple of resources that could elicit some introspection and
> > (re-)thinking of existing practices:
>
> It is even less effective.  Friday may be bad and many people may
> agree to avoid Friday releases.

Thank you for your honesty. I want to share that I have spent considerable
time reflecting on the release process because I genuinely care about
improving it both for the sake of Git's users as well as its contributors.
I've thoughtfully weighed the challenges -- like having clear and
dependable timelines, like timing releases around holidays, weekends, and
accommodating embargoed releases -- and observe significant room for
improvement.

I approached writing the email to which you replied with the intention of
fostering a collaborative discussion. I put a lot of effort into crafting
my thoughts constructively, writing and rewriting the email, even deleting
several well-laid out arguments in the interest of a less confrontational
and dismissive tone in favor of inspiring reflection, and I had hoped for
a response that mirrored that level of consideration.

That said, I am eager to hear your thoughts on how we can shift this
dialogue into a more productive and collaborative direction, one where we
focus on enhancing the project together.

> So what is your preference?

Apart from seeing the need to improve on the status quo, I have no fixed
preference. How do _you_ envision a release process that could better
serve the needs of everyone involved?

Looking forward to hearing your insights,
Johannes

> In any case, I'll go back to my vacation ;-)

I hope it was a good, relaxing one, that helped you un- and rewind.

  reply	other threads:[~2025-03-26  7:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 16:22 Git Bug Report: git add --patch > "e" makes keyboard unresponsive Dan Demp
2024-04-24 21:54 ` brian m. carlson
2024-04-24 22:23   ` Junio C Hamano
2024-04-25  4:13     ` Dan Demp
2024-04-25  4:24       ` Junio C Hamano
2024-04-25  4:15     ` Dan Demp
2025-03-16  3:34 ` Johannes Schindelin
2025-03-17 22:24   ` Junio C Hamano
2025-03-25 11:23     ` Releasing versions on Fridays, was " Johannes Schindelin
2025-03-25 11:44       ` Junio C Hamano
2025-03-26  7:02         ` Johannes Schindelin [this message]
2025-03-26  7:53           ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c4753c0d-d957-c4d0-a452-1e592cade34f@gmx.de \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).