All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: 2.43 release date adjustment?
Date: Wed, 23 Aug 2023 09:20:33 -0700	[thread overview]
Message-ID: <xmqqpm3dg27i.fsf@gitster.g> (raw)
In-Reply-To: <ZOYdG8RtPIgymtBV@nand.local> (Taylor Blau's message of "Wed, 23 Aug 2023 10:52:11 -0400")

Taylor Blau <me@ttaylorr.com> writes:

> Now that we're on the other side of 2.42, it looks like the tentative
> release date for 2.43 has been scheduled for 2023-11-20.
>
> That week is a US holiday (Thanksgiving, on 2023-11-23). I figure that
> many US-based folks may take a good portion of if not the whole week
> off.

True.

> Should we consider pushing back the release to the week after
> Thanksgiving, say on 2023-11-27? This cycle is already somewhat long so
> we could move the release up to 2023-11-13, but I think it would be
> nice to have folks around in case of any brown paper-bag fixes.

I am not sure how it would help to place the release day immediately
after the off-week everybody has stayed off the keyboard, though.  I
would prefer to see fully working weeks during the pre-release
period so that people can work on last minute regression fixes, so I
hoped it would work much better to release before the holiday week
begins, rather than after it ends.

But of course I am open to inputs.  FYI, I plan to be offline _after_
the Thanksgiving week.


  reply	other threads:[~2023-08-23 16:20 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 [this message]
2023-08-23 18:37   ` Taylor Blau
2023-08-23 21:39     ` Junio C Hamano
2023-08-23 21:47       ` Taylor Blau
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=xmqqpm3dg27i.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.