Subject: Re: [PATCH RFC v4 7/9] BreakingChanges: announce Rust becoming mandatory

From: Junio C Hamano <[email-masked]>
Date: Wed, 24 Sep 2025 10:43:14 -0700

Patrick Steinhardt <[email-masked]> writes:

> So maybe it's premature at the current point in time to already spell
> out details. Should we maybe just defer that decision into the future?
> E.g. something like the below patch.
>
> Patrick
>
> diff --git a/Documentation/BreakingChanges.adoc b/Documentation/BreakingChanges.adoc
> index 3b54750621..bf3173013d 100644
> --- a/Documentation/BreakingChanges.adoc
> +++ b/Documentation/BreakingChanges.adoc
> @@ -200,9 +200,9 @@ The Git project will declare the last version before Git 3.0 to be a long-term
>  support release. This long-term release will receive important bug fixes for at
>  least four release cycles and security fixes for six release cycles. The Git
>  project will hand over maintainership of the long-term release to distributors
> -in case they need to extend the life of that long-term release even further. In
> -that case, the backporting process will be handled by these distributors, but
> -the long-term release tags will be created in the canonical Git repository.
> +in case they need to extend the life of that long-term release even further.
> +Details of how this long-term release will be handed over to the community will
> +be decided once the Git project decides to stop officially supporting it.
>  +
>  We will evaluate the impact on downstream distributions before making Rust
>  mandatory in Git 3.0. If we see that the impact on downstream distributions

Yup, punting on this would not hurt our overall timeline, so let's
achieve concensus on other parts of the document and the patches.

Thanks.