Hi Junio, On Mon, 17 Mar 2025, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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
