git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Releasing versions on Fridays, was Re: Git Bug Report: git add --patch > "e" makes keyboard unresponsive

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 26, 2025, 07:02 UTC
Message-ID
<c4753c0d-d957-c4d0-a452-1e592cade34f@gmx.de>
In-Reply-To
<xmqqsen1mj1y.fsf@gitster.g>
Hi Junio,
On Tue, 25 Mar 2025, Junio C Hamano wrote:
Show 10 quoted lines
> 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.
Previous: Junio C HamanoNext: Junio C Hamano
Message 11 of 12 in “Git Bug Report: git add --patch > "e" makes keyboard unresponsive”
  1. Dan DempApr 24, 2024
  2. brian m. carlsonApr 24, 2024
  3. Junio C HamanoApr 24, 2024
  4. Dan DempApr 25, 2024
  5. Junio C HamanoApr 25, 2024
  6. Dan DempApr 25, 2024
  7. Johannes SchindelinMar 16, 2025
  8. Junio C HamanoMar 17, 2025
  9. Releasing versions on Fridays, was Re: Git Bug Report: git add --patch > "e" makes keyboard unresponsiveJohannes Schindelin, Mar 25, 2025
  10. Junio C HamanoMar 25, 2025
  11. Johannes SchindelinMar 26, 2025
  12. Junio C HamanoMar 26, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.