git.vger.kernel.org archive mirror
 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 15:03:45 -0700	[thread overview]
Message-ID: <xmqqcyzde7r2.fsf@gitster.g> (raw)
In-Reply-To: <ZOZ+cbkrXsEcQyaW@nand.local> (Taylor Blau's message of "Wed, 23 Aug 2023 17:47:29 -0400")

Taylor Blau <me@ttaylorr.com> writes:

> 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.

That is exactly what I call "expecting a post-release fixes".

A much more important thing is to make sure we catch them before the
release and devise ways to help us do so, perhaps opting more userbase
into testing early.

Also a much more productive thing to discuss than just the timeline:
What do we want the end product of this cycle to include?

I am personally hoping to see an enhanced rerere that can record and
replay delete-modify conflict that gets resolved to removal.  Others
may have their own agenda, and it may be interesting to hear them.
Those without specific agenda for this cycle may volunteer to help
others' topics.

Thanks.

  reply	other threads:[~2023-08-23 22:04 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
2023-08-23 22:03         ` Junio C Hamano [this message]
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=xmqqcyzde7r2.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).