# Git 2.41 release date

3 messages from 2023-03-22 to 2023-03-23. Participants: Victoria Dye, Junio C Hamano.
Thread: https://gitlist.dev/t/59444

## Victoria Dye, 2023-03-22 17:59

Subject: Git 2.41 release date
Message-ID: <f337e514-8d3b-927a-5fe3-34f67f199435@github.com>
URL: https://gitlist.dev/e/f337e514-8d3b-927a-5fe3-34f67f199435%40github.com

```
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

```

## Junio C Hamano, 2023-03-22 19:16

Subject: Re: Git 2.41 release date
Message-ID: <xmqq7cv8egvu.fsf@gitster.g>
URL: https://gitlist.dev/e/xmqq7cv8egvu.fsf%40gitster.g
In-Reply-To: <f337e514-8d3b-927a-5fe3-34f67f199435@github.com>

```
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?

```

## Victoria Dye, 2023-03-23 04:27

Subject: Re: Git 2.41 release date
Message-ID: <48664dbe-b777-1019-8941-e2948dd55f53@github.com>
URL: https://gitlist.dev/e/48664dbe-b777-1019-8941-e2948dd55f53%40github.com
In-Reply-To: <xmqq7cv8egvu.fsf@gitster.g>

```
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.


```
