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 14:39:41 -0700 [thread overview]
Message-ID: <xmqqh6ope8v6.fsf@gitster.g> (raw)
In-Reply-To: ZOZR0jesPpCDNbRj@nand.local
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?
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.
The users will be taking the holiday week and will be slow after the
release anyway, and developers work should also happen more before
the release and not after it, no?
next prev parent reply other threads:[~2023-08-23 21:41 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 [this message]
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=xmqqh6ope8v6.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 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).