Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08)
Date: Thu, 24 Sep 2026 10:00:02 -0700	[thread overview]
Message-ID: <xmqqy0cq37ql.fsf@gitster.g> (raw)
In-Reply-To: <306e7563-c356-dc59-c14a-ff8e99a948ae@gmx.de> (Johannes Schindelin's message of "Thu, 24 Sep 2026 14:29:01 +0200 (CEST)")

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

>> So the above is what I have in mind, shaped mostly around the
>> consensus at the Contributors' Summit (or at least how I understand
>> what the consensus was), with my preference filling in what was not
>> firmly decided in the room.
>
> Thank you so much! This will make it much easier for me to plan out the
> Git for Windows roadmap, such as switching to Rust-based builds and
> integrating Git Credential Manager v3.0.

Note that I consider it risky to treat the timeline as already set
in stone.

In particular, if we find that 2.99 needs a longer stabilization
effort, we may need to slip 2.99.1 by a month or follow it with
2.99.2 or even 2.99.3, and 3.0 may have to coincide with one of
these later maintenance releases.  Anything beyond the end of this
year is in "we do not yet know and we will play it by ear when the
time comes" territory.

Thanks.

  reply	other threads:[~2026-09-24 17:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  0:11 What's cooking in git.git (Sep 2026, #08) Junio C Hamano
2026-09-22  8:11 ` kh/format-patch-range-diff-notes Kristoffer Haugsbakk
2026-09-22 13:25 ` Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08) Johannes Schindelin
2026-09-22 13:49   ` Junio C Hamano
2026-09-22 17:06     ` Johannes Schindelin
2026-09-24  3:56       ` Junio C Hamano
2026-09-24  4:30         ` Junio C Hamano
2026-09-24 12:29           ` Johannes Schindelin
2026-09-24 17:00             ` Junio C Hamano [this message]
2026-09-24 18:08           ` Ramsay Jones
2026-09-22 18:44     ` My summary of the Git Contributors' Summit 2026, was " Johannes Schindelin
2026-09-23 11:55       ` Daniele Sassoli
2026-09-24 12:31         ` Johannes Schindelin
2026-09-25  9:53         ` Luca Milanesio
2026-09-23 12:52       ` D. Ben Knoble
2026-09-23 14:22       ` Security mailing list & process, was Re: My summary of the Git Contributors' Summit 2026 Toon Claes
2026-09-24 12:38         ` Johannes Schindelin
2026-09-23 14:40       ` Git Contributor' summit: Documentation, was: Re: 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) Toon Claes
2026-09-23 15:15         ` Git Contributor' summit: Documentation, Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqy0cq37ql.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox