Re: [PATCH v6 1/4] docs: introduce document to announce breaking changes
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 4, 2024, 17:59 UTC
- Message-ID
- <xmqqsexsvbaf.fsf@gitster.g>
- In-Reply-To
- <a260bbf281d2975562a042a71ca0dd7f88f03da4.1717504292.git.ps@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
> +* Git 1.6, released in August 2008. In retrospect, this release should likely > + have bumped the major version.
No need to reroll just for this alone, but back then, a non-zero third component did not mean they are maintenance releases (e.g., v1.5.3.3 was the third maintenance update for the v1.5.3 series) and v1.6.0 _was_ a departure, a breaking change from the v1.5.x series.
It is more recent tradition that we only use three numbers. I'd strike the whole "In retrospect" comment if I were writing this.
> +to see the message and its surrounding discussion. Such a reference is there to > +make it easier for you to find how the project reached concensus on the
"concensus" -> "consensus".