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, 21:39 UTC
Message-ID
<xmqqh6ope8v6.fsf@gitster.g>
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?

Previous: Taylor BlauNext: Taylor Blau
Message 4 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.