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

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 22, 2026, 13:49 UTC
Message-ID: <xmqq4ifhgzvx.fsf@gitster.g>
In-Reply-To: <76ac51df-cef8-c6a9-2610-8c21f03c6999@gmx.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 15 quoted lines

> Hi Junio,
>
> 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.

Show 5 quoted lines

> Rust was treated as mandatory for v3.0, and the explicit check for
> objections drew none from anyone in the room. Compared with the
> contentious portability discussion on the Git mailing list, that is a
> notable signal. It does not establish that the portability problems
> themselves are solved.

It signals that the room was smaller than the list. Or enough time passed since we discussed some minority platforms having trouble with Rust the last time to change the situation. Or little bit of both ;-)

Thanks.