Re: [PATCH v6 1/4] docs: introduce document to announce breaking changes

From: Patrick Steinhardt <ps@pks.im>
Date: Jun 5, 2024, 05:31 UTC
Message-ID: <Zl_4IIqFmoPhx1Gc@tanuki>
In-Reply-To: <xmqqsexsvbaf.fsf@gitster.g>

On Tue, Jun 04, 2024 at 10:59:52AM -0700, Junio C Hamano wrote:

Show 12 quoted lines

> 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.

The reason why I included it is that I didn't want to create the impression that breaking releases may also happen when bumping the second version component. It did happen with v1.6.0, but in the future I think we'd want to always bump the first component on such releases, do we?

Patrick