Re: An early draft of v1.5.0 release notes (2nd ed)

From: Junio C Hamano <junkio@cox.net>
Date: Dec 28, 2006, 05:54 UTC
Message-ID: <7vhcvg1s6o.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20061228024719.GG16612@spearce.org>

Shawn Pearce <spearce@spearce.org> writes:

Show 14 quoted lines

> Junio C Hamano <junkio@cox.net> wrote:
>> Shawn Pearce <spearce@spearce.org> writes:
>> 
>> > The section is really for those who are upgrading from ancient
>> > versions, but the title of the section implies (at least to me)
>> > that these changes aren't something important.
>> 
>> True.  How about "Something important you should already know
>> but just in case" ;-)?
>
> Sure, that's more fun then my proposed text and does summarize the
> section better.  Plus it reminds Git users that maybe they should
> track our releases a little bit more often than only on "major"
> version number increments.  :-)

That was a tongue-in-cheek comment.

I consider git is still young and I have the right to gripe at the list if something that has been cooking in 'next' without anybody complaining causes a real breakage immediately after it gets pushed out to 'master'. But for the rest of the world, git has already matured enough that there is much less need to be on the bleeding edge for the lack of something crucial in the last released version.

And let's face it. Nobody has enough time to keep track of the changes to all tools he uses, it is not unusual to skip a handful of minor versions, and it is a norm to get surprised after an upgrade of any tool because there was a major change in a couple of releases back that he skipped. I do not have the right to complain if the end users do not follow every minor release or every issue of "What's in git.git" messages. Not anymore.

So I'd like the introductory section to have more positive spin. I tried rewording it and pushed it out to 'todo' branch.