Re: What will come after Git 2.56?

[Junio C Hamano <gitster@pobox.com>]

Harald Nordgren <haraldnordgren@gmail.com> writes:

>> Well, same as there's room after Git 2.9 we also still have room after
>> Git 2.99. No reason we cannot have Git 2.100. :)
>
> I agree completely, no need signal that 3.0 is coming until it comes. Once it's
> out, not a soul will question what number the release just before had.

I am afraid you totally misunderstand what we are doing.  Once it is
out nobody would care, but that completely misses the point.

By giving "Something big is coming" beforehand, we are warning
downstream projects and distributions an advance warning and that
begins with the jump from 2.5X to 2.98.

> I have a list of breaking changes that I would like to introduce, I was hoping
> they could be considered before 3.0 is out -- otherwise I fear I have to wait
> another 10 years for 4.0, I would like to change the default values of these
> config values:

I do not know how long it will be before 4.0, but if you do not have
any draft code on the list or even design presented before this
message, it is way too late for 3.0.  No, these won't be part of it.

But some may not even qualify as "breaking changes", so after 3.0,
some of them may not have to wait until 4.0 happens.