{"thread":{"id":"59444","subject":"Git 2.41 release date","startedAt":"2023-03-22T17:59:57Z","lastAt":"2023-03-23T04:28:43Z","messageCount":3,"participants":["Victoria Dye","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"473950","messageId":"f337e514-8d3b-927a-5fe3-34f67f199435@github.com","threadId":"59444","inReplyTo":null,"subject":"Git 2.41 release date","fromName":"Victoria Dye","fromEmail":"vdye@github.com","sentAt":"2023-03-22T17:59:50Z","receivedAt":"2023-03-22T17:59:57Z","isPatch":false,"sender":{"key":"vdye@github.com","avatar":"https://avatars.githubusercontent.com/u/3619353?v=4"},"body":"Hi everyone! \n\nWhile perusing the Git Calendar [1], I noticed that the final 2.41 release\ndate is on a major US holiday (Memorial Day, May 29). In the past, release\ndates have been shifted to avoid situations like this, and doing so has been\nnoticeably helpful to downstream maintainers/integrators. Would it make\nsense to similarly shift 2.41?\n\nThanks,\n-Victoria \n\n[1] https://calendar.google.com/calendar/u/0/embed?src=jfgbl2mrlipp4pb6ieih0qr3so@group.calendar.google.com\n"},{"id":"473953","messageId":"xmqq7cv8egvu.fsf@gitster.g","threadId":"59444","inReplyTo":"f337e514-8d3b-927a-5fe3-34f67f199435@github.com","subject":"Re: Git 2.41 release date","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-03-22T19:16:21Z","receivedAt":"2023-03-22T19:16:26Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Victoria Dye <vdye@github.com> writes:\n\n> While perusing the Git Calendar [1], I noticed that the final 2.41 release\n> date is on a major US holiday (Memorial Day, May 29). In the past, release\n> dates have been shifted to avoid situations like this, and doing so has been\n> noticeably helpful to downstream maintainers/integrators. Would it make\n> sense to similarly shift 2.41?\n\nSurely, I will be accomodating, of course.  Thanks for spotting.\n\nHow does Thu June 1st sound?\n"},{"id":"473976","messageId":"48664dbe-b777-1019-8941-e2948dd55f53@github.com","threadId":"59444","inReplyTo":"xmqq7cv8egvu.fsf@gitster.g","subject":"Re: Git 2.41 release date","fromName":"Victoria Dye","fromEmail":"vdye@github.com","sentAt":"2023-03-23T04:27:19Z","receivedAt":"2023-03-23T04:28:43Z","isPatch":false,"sender":{"key":"vdye@github.com","avatar":"https://avatars.githubusercontent.com/u/3619353?v=4"},"body":"Junio C Hamano wrote:\n> Victoria Dye <vdye@github.com> writes:\n> \n>> While perusing the Git Calendar [1], I noticed that the final 2.41 release\n>> date is on a major US holiday (Memorial Day, May 29). In the past, release\n>> dates have been shifted to avoid situations like this, and doing so has been\n>> noticeably helpful to downstream maintainers/integrators. Would it make\n>> sense to similarly shift 2.41?\n> \n> Surely, I will be accomodating, of course.  Thanks for spotting.\n> \n> How does Thu June 1st sound?\n\nThank you so much! June 1st sounds great.\n\n"}]}