[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTi=Rky8zGrJ7TSF0MumzQWjpsD7Lcw@mail.gmail.com>
Date: Tue, 24 May 2011 14:48:08 -0400
From: eschvoca <eschvoca@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "H. Peter Anvin" <hpa@...or.com>,
"jonsmirl@...il.com" <jonsmirl@...il.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Jacek Luczak <difrost.kernel@...il.com>,
Jan Engelhardt <jengelh@...ozas.de>,
linux-arch@...r.kernel.org, linux-mm <linux-mm@...ck.medozas.de>,
"Ted Ts'o" <tytso@....edu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
DRI <dri-devel@...ts.freedesktop.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: (Short?) merge window reminder
On Tue, May 24, 2011 at 1:41 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Tue, May 24, 2011 at 10:36 AM, H. Peter Anvin <hpa@...or.com> wrote:
>>
>> I think this whole discussion misses the essence of the new development
>> model, which is that we no longer do these kinds of feature-based major
>> milestones.
>
> Indeed.
>
> It's not about features. It hasn't been about features for forever.
>
> So a renumbering would be purely about dropping the numbers to
> something smaller and more easily recognized. The ABI wouldn't change.
> The API wouldn't change. There wouldn't be any big "because we finally
> did xyz".
>
Me, a nobody end user, would prefer a version number that corresponded
to the date. Something like:
%y.%m.<stable patch>
%Y.%m.<stable patch>
Then users would know the significance of the number and when a vendor
says they support Linux 11.09 the user will immediately know if they
are up to date.
Using the date also clearly communicates it is not about features.
When there is a 3.0 (4.0) release people expect big new features and
API/ABI breakage.
My 2 cents.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists