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

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 25, 2025, 11:23 UTC
Message-ID
<2dd6e0fa-b997-f69c-874b-f424325123a8@gmx.de>
In-Reply-To
<xmqqsenb70u0.fsf@gitster.g>
Hi Junio,
On Mon, 17 Mar 2025, Junio C Hamano wrote:
Show 14 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > I refused to release on a Friday (absent any good reason) which is why
> > this version is scheduled to appear this coming Monday.
>
> Not on-topic for any particular bug, but do you want to probably
> coordinate on what day of the week a release is made, perhaps?  I've
> been trying to stick to the same time-of-the-day we established
> earlier for embargoed coordinated releases, which is 1700 UTC - 2600
> Asia/Tokyo.  But the choice of the day-of-the-week has been more or
> less arbitrary picked by me to happen on Fridays for the past few
> releases; it seems 2.47 was done on Monday.
>
> Any preferences?

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:

- https://daniel.haxx.se/blog/2022/08/16/the-curl-release-cycle/
- https://www.researchgate.net/publication/268815678_Why_and_How_Should_Open_Source_Projects_Adopt_Time-Based_Releases
  (old, still relevant)
- Notice the weekday when Firefox releases new versions:
  https://www.mozilla.org/en-US/firefox/releases/
- https://msrc.microsoft.com/blog/2023/11/reflecting-on-20-years-of-patch-tuesday/
- https://www.linkedin.com/pulse/best-day-week-release-software-rajith-muditha-attapattu-wvpuc
- https://corner.buka.sh/why-dont-deploy-on-friday-is-more-than-just-a-superstition/
  (yes, new Git releases can elicit support escalations on weekends)
- https://www.wingravity.com/blog/deploying-on-a-friday-to-risk-or-not-to-risk
- https://www.sinergiapositiva.com/2024/11/19/friday-deployments-arent-the-issue-your-quality-processes-are/

Ciao, Johannes

Previous: Junio C HamanoNext: Junio C Hamano
Message 9 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.