From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: 2.43 release date adjustment?
Date: Wed, 23 Aug 2023 10:52:11 -0400 [thread overview]
Message-ID: <ZOYdG8RtPIgymtBV@nand.local> (raw)
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.
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.
Thanks,
Taylor
next reply other threads:[~2023-08-23 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:52 Taylor Blau [this message]
2023-08-23 16:20 ` 2.43 release date adjustment? 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
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=ZOYdG8RtPIgymtBV@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
/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).