From: Luca Milanesio <luca.milanesio@gmail•com>
To: git@vger•kernel.org
Cc: Luca Milanesio <luca.milanesio@gmail•com>
Subject: Re: When should we release Git 3.0?
Date: Wed, 1 Oct 2025 08:13:12 +0100 [thread overview]
Message-ID: <E03F997F-1738-4CF6-B7D5-206183FA5BD1@gmail.com> (raw)
In-Reply-To: <aNxivuJEnSHbQNdr@fruit.crustytoothpaste.net>
> On 1 Oct 2025, at 00:07, brian m. carlson <sandals@crustytoothpaste•net> wrote:
>
> There's been discussion at the Contributor Summit about when we should
> release Git 3.0. The original plan that was discussed was to release in
> about a year, which is about 4 releases away.
>
> Almost all of the functionality that we had wanted in Git 3.0 has been
> implemented. The two major things we may want to consider as blockers
> for Git 3.0 are the following:
>
> * The SHA-256 interoperability work is not done yet. My estimate of
> this work is 200–400 patches, of which about 100 are done. If the
> original schedule is maintained, this would require writing up to 75
> patches and sending in 100 patches per cycle, which is unrealistic
> without additional contributors.
> * Some forges and other projects do not yet have full SHA-256 support.
> It's my understanding that all of the major forges are undertaking or
> have undertaken this work and are at various levels of completion, but
> it's not clear that other projects have appropriate support.
>
> We may also wish to stick to a stricter timeframe for this release
> regardless and make four releases from now or the next release a year
> away Git 3.0 regardless of whether those items above are completed.
I apologise to not have participated to the Contributor Summit, I just joined the Git Mini-Summit in Amsterdam and we discussed briefly Gerrit 3.0 over dinner, but not with such a detail.
Do you have the notes or recording of the discussion?
I am worried that if we rush into Git 3.0 with breaking changes that would make other “forges” (e.g. JGit) incompatible, we would be in a difficult situation with the other Git ecosystem that isn’t based on the C-Git implementation.
> Discussions at the Contributor Summit did mention the advantage of
> having a hard deadline would be that it would make projects and forges
> spend the time to implement SHA-256 support if they're lacking it.
Happy to spend more time on it, I believe Nasser and Martin from the JGit project attended in-person yesterday.
Any commitment from your side? Do you have budget from your $DAY_JOB?
> I personally do not want the interoperability work to be a blocker. I
> haven't really heard other commitments of contributors who want to work
> on it and I don't really want to have to run full tilt trying to get it
> out. However, some other people may feel differently, in which I case I
> encourage their participation in the project.
Sure, happy to participate.
Luca.
next prev parent reply other threads:[~2025-10-01 7:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 23:07 When should we release Git 3.0? brian m. carlson
2025-10-01 7:13 ` Luca Milanesio [this message]
2025-10-01 16:04 ` Taylor Blau
2025-10-01 19:31 ` rsbecker
2025-10-08 21:44 ` Taylor Blau
2025-10-08 21:55 ` rsbecker
2025-10-02 13:31 ` Patrick Steinhardt
2025-10-02 15:32 ` Junio C Hamano
2025-10-02 16:10 ` Michal Suchánek
2025-10-07 10:27 ` Patrick Steinhardt
2025-10-07 10:36 ` Michal Suchánek
2025-10-07 13:21 ` Patrick Steinhardt
2025-10-07 13:40 ` Michal Suchánek
2025-10-07 17:11 ` Junio C Hamano
2025-10-07 17:28 ` Michal Suchánek
2025-10-08 20:44 ` SZEDER Gábor
2025-10-09 5:56 ` Patrick Steinhardt
2025-10-02 16:54 ` Ben Knoble
2025-10-07 10:27 ` Patrick Steinhardt
2025-10-07 17:36 ` rsbecker
2025-10-08 22:05 ` Taylor Blau
2025-10-09 5:59 ` Patrick Steinhardt
2025-10-16 21:32 ` brian m. carlson
2025-10-08 21:59 ` Taylor Blau
2025-10-16 21:42 ` brian m. carlson
2025-10-02 22:33 ` brian m. carlson
2025-10-01 16:01 ` Taylor Blau
2025-10-01 16:20 ` Michal Suchánek
2025-10-01 22:16 ` brian m. carlson
2025-10-02 12:13 ` Michal Suchánek
2025-10-02 13:09 ` Michal Suchánek
2025-10-01 20:36 ` Junio C Hamano
2025-10-01 22:42 ` brian m. carlson
-- strict thread matches above, loose matches on Subject: below --
2025-10-08 19:06 James Frost
2025-10-09 5:30 ` Patrick Steinhardt
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=E03F997F-1738-4CF6-B7D5-206183FA5BD1@gmail.com \
--to=luca.milanesio@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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