On Wed, Aug 23, 2023 at 02:39:41PM -0700, Junio C Hamano wrote: > Taylor Blau <me@xxxxxxxxxxxx> writes: > > > Perhaps then we should shorten this cycle by a week and plan to cut the > > release on 2023-11-13. > > I still do not see the point. Do you mean you do not want to work > between 13th to 17th of November that would be the "final regression > hunt in -rc2" week? That wasn't quite what I was saying, but maybe I am just confused by what you mean. I am suggesting cutting the release on the 13th of November instead of the 20th so that we have folks online for the first week after the release tag is pushed out to fix any brown-paper-bag issues. Then, after the release is no longer fresh, we can expect many US developers to take the week of the 20th off. > If you have a specific reason to expect a post-release bug hunt, > that would change the equation, but otherwise, I am not sure what > you are trying to achieve, compared to the original plan to tag on > 20th, give developers week off after the release for Thanksgiving or > whatever the excuse to take a week off in your parts of the world. No specific reason to expect bugs. Just trying to line things up so that we have (a) people around when the release is tagged, and (b) don't have a release hanging over our heads either during or immediately after a week when most US developers are offline. Thanks, Taylor
