* Git 2.41 release date
@ 2023-03-22 17:59 Victoria Dye
2023-03-22 19:16 ` Junio C Hamano
0 siblings, 1 reply; 3+ messages in thread
From: Victoria Dye @ 2023-03-22 17:59 UTC (permalink / raw)
To: Git Mailing List; +Cc: Junio C Hamano, Johannes Schindelin, Derrick Stolee
Hi everyone!
While perusing the Git Calendar [1], I noticed that the final 2.41 release
date is on a major US holiday (Memorial Day, May 29). In the past, release
dates have been shifted to avoid situations like this, and doing so has been
noticeably helpful to downstream maintainers/integrators. Would it make
sense to similarly shift 2.41?
Thanks,
-Victoria
[1] https://calendar.google.com/calendar/u/0/embed?src=jfgbl2mrlipp4pb6ieih0qr3so@group.calendar.google.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Git 2.41 release date
2023-03-22 17:59 Git 2.41 release date Victoria Dye
@ 2023-03-22 19:16 ` Junio C Hamano
2023-03-23 4:27 ` Victoria Dye
0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2023-03-22 19:16 UTC (permalink / raw)
To: Victoria Dye; +Cc: Git Mailing List, Johannes Schindelin, Derrick Stolee
Victoria Dye <vdye@github.com> writes:
> While perusing the Git Calendar [1], I noticed that the final 2.41 release
> date is on a major US holiday (Memorial Day, May 29). In the past, release
> dates have been shifted to avoid situations like this, and doing so has been
> noticeably helpful to downstream maintainers/integrators. Would it make
> sense to similarly shift 2.41?
Surely, I will be accomodating, of course. Thanks for spotting.
How does Thu June 1st sound?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Git 2.41 release date
2023-03-22 19:16 ` Junio C Hamano
@ 2023-03-23 4:27 ` Victoria Dye
0 siblings, 0 replies; 3+ messages in thread
From: Victoria Dye @ 2023-03-23 4:27 UTC (permalink / raw)
To: Junio C Hamano; +Cc: Git Mailing List, Johannes Schindelin, Derrick Stolee
Junio C Hamano wrote:
> Victoria Dye <vdye@github.com> writes:
>
>> While perusing the Git Calendar [1], I noticed that the final 2.41 release
>> date is on a major US holiday (Memorial Day, May 29). In the past, release
>> dates have been shifted to avoid situations like this, and doing so has been
>> noticeably helpful to downstream maintainers/integrators. Would it make
>> sense to similarly shift 2.41?
>
> Surely, I will be accomodating, of course. Thanks for spotting.
>
> How does Thu June 1st sound?
Thank you so much! June 1st sounds great.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-03-23 4:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-03-22 17:59 Git 2.41 release date Victoria Dye
2023-03-22 19:16 ` Junio C Hamano
2023-03-23 4:27 ` Victoria Dye
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).