git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: 2.43 release date adjustment?

From
Taylor Blau <me@ttaylorr.com>
Date
Aug 23, 2023, 22:34 UTC
Message-ID
<ZOaJXSZu4Bv6aXEH@nand.local>
In-Reply-To
<xmqqcyzde7r2.fsf@gitster.g>
On Wed, Aug 23, 2023 at 03:03:45PM -0700, Junio C Hamano wrote:
Show 12 quoted lines
> 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.

I agree, but shouldn't we still plan such that we have folks around for a week after the release in case something was missed?

Thanks, Taylor

Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 8 in “2.43 release date adjustment?”
  1. Taylor BlauAug 23, 2023
  2. Junio C HamanoAug 23, 2023
  3. Taylor BlauAug 23, 2023
  4. Junio C HamanoAug 23, 2023
  5. Taylor BlauAug 23, 2023
  6. Junio C HamanoAug 23, 2023
  7. Taylor BlauAug 23, 2023
  8. Junio C HamanoAug 24, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.