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

Re: Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 22, 2026, 17:06 UTC
Message-ID
<5f34a5a9-9f72-b725-666a-94798895d122@gmx.de>
In-Reply-To
<xmqq4ifhgzvx.fsf@gitster.g>
Hi Junio,
On Tue, 22 Sep 2026, Junio C Hamano wrote:
Show 22 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > On Mon, 21 Sep 2026, Junio C Hamano wrote:
> >
> >> Git 2.56-rc1 has been tagged.  We may merge last-minute fixes before
> >> the final Git 2.56 release, but otherwise I do not expect any new
> >> feature topics to be ready before the final, so most of the
> >> in-flight topics will stay cooking in 'next' until then.  As
> >> discussed at the Git Contributors' Summit, the version after the
> >> upcoming Git 2.56 will be Git 2.98, scheduled near the end of this
> >> year.
> >
> > Would you say that the following is an accurate characterization of the
> > timeline, so that people who need to plan dependent projects can rely on
> > it?
> 
> My outline was deliberately limited up to end of this year as I am
> hesitant to say beyond that point before the meeting notes are made
> public.  I am not sure who will be releasing it to the public and
> when, though with the open nature of this community I believe it
> will happen soon.  I do not recall anything controversial in the 3.0
> section of the meeting notes.

Fair enough: I did ask you to confirm my summit summary. Let me separate that from what I need for planning: a proposal from you as release maintainer can be discussed on the list on its own merits, without waiting for publication of the meeting record or claiming summit consensus.

Could you use the next What's cooking to outline your working release plan: whether paired 2.99.1/3.0 releases in March or April 2027 would be your proposed target, what conditions could move it, and when we should review that target?

If you cannot yet choose a target, could that update identify what needs resolving and when you expect to revisit the choice?

Your assessment would give dependent projects a common baseline to coordinate around. A provisional planning assumption would be useful; it need not be a guarantee.

Thanks, Johannes

Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 19 in “What's cooking in git.git (Sep 2026, #08)”
  1. Junio C HamanoSep 22, 2026
  2. kh/format-patch-range-diff-notesKristoffer Haugsbakk, Sep 22, 2026
  3. Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08)Johannes Schindelin, Sep 22, 2026
  4. Junio C HamanoSep 22, 2026
  5. Johannes SchindelinSep 22, 2026
  6. Junio C HamanoSep 24, 2026
  7. Junio C HamanoSep 24, 2026
  8. Johannes SchindelinSep 24, 2026
  9. Junio C HamanoSep 24, 2026
  10. Ramsay JonesSep 24, 2026
  11. My summary of the Git Contributors' Summit 2026, was Re: Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08)Johannes Schindelin, Sep 22, 2026
  12. Daniele SassoliSep 23, 2026
  13. Johannes SchindelinSep 24, 2026
  14. Luca MilanesioSep 25, 2026
  15. D. Ben KnobleSep 23, 2026
  16. Toon ClaesSep 23, 2026
  17. Johannes SchindelinSep 24, 2026
  18. Toon ClaesSep 23, 2026
  19. Junio C HamanoSep 23, 2026

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.