git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: 2.43 release date adjustment?
Date: Wed, 23 Aug 2023 17:47:29 -0400	[thread overview]
Message-ID: <ZOZ+cbkrXsEcQyaW@nand.local> (raw)
In-Reply-To: <xmqqh6ope8v6.fsf@gitster.g>

On Wed, Aug 23, 2023 at 02:39:41PM -0700, Junio C Hamano wrote:
> Taylor Blau <me@ttaylorr.com> 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

  reply	other threads:[~2023-08-23 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 14:52 2.43 release date adjustment? Taylor Blau
2023-08-23 16:20 ` Junio C Hamano
2023-08-23 18:37   ` Taylor Blau
2023-08-23 21:39     ` Junio C Hamano
2023-08-23 21:47       ` Taylor Blau [this message]
2023-08-23 22:03         ` Junio C Hamano
2023-08-23 22:34           ` Taylor Blau
2023-08-24  1:21             ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZOZ+cbkrXsEcQyaW@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).