Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: What will come after Git 2.56?
Date: Sun, 06 Sep 2026 00:03:20 -0700	[thread overview]
Message-ID: <xmqqmrtu50av.fsf@gitster.g> (raw)

http://tinyurl.com/gitcal tells us that the current development
cycle for Git 2.56 will conclude around the end of this month.  As
our typical development cycle lasts between 8 and 12 weeks, we will
have exactly one more cycle after that before the end of the year.

Now, the question is what that release should be called.  A few
thoughts.

 (1) Git 3.0: it is tempting to conclude the year with a big
     version bump.  Splash!

 (2) Git 2.99: by leaving no more room until 3.0, we will
     conclude the year with a version that is still in the 2.X
     series, but will hopefully force us to seriously prepare for
     a big version bump with the first release of the year 2027.

 (3) Git 2.98 (or 2.97): we admit that we are not ready for even
     (2) and chicken out, leaving us breathing room for a few
     more preparatory releases before the big one.

 (4) Git 2.57: doing business as usual.

Needless to say, this is not a popularity contest, nor is it even a
democracy.  Regardless, we should review what we have in the
'BreakingChanges' document and ask ourselves how ready we are.


             reply	other threads:[~2026-09-06  7:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06  7:03 Junio C Hamano [this message]
2026-09-06 18:14 ` What will come after Git 2.56? brian m. carlson
2026-09-07  8:23   ` Patrick Steinhardt
2026-09-07  9:30   ` Emily Shaffer
2026-09-08 15:46   ` rsbecker
2026-09-08 15:59     ` brian m. carlson

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=xmqqmrtu50av.fsf@gitster.g \
    --to=gitster@pobox.com \
    --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