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

Re: 2.43 release date adjustment?

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 23, 2023, 22:03 UTC
Message-ID
<xmqqcyzde7r2.fsf@gitster.g>
In-Reply-To
<ZOZ+cbkrXsEcQyaW@nand.local>
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.
Previous: Taylor BlauNext: Taylor Blau
Message 6 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.