From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: "Artem S. Tashkinov" <t.artem@lycos.com>
Cc: Tejun Heo <htejun@gmail.com>,
kevin granade <kevin.granade@gmail.com>,
linux-kernel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: On Linux numbering scheme
Date: Mon, 25 Oct 2010 12:04:38 +0200 [thread overview]
Message-ID: <1288001078.17570.24.camel@thorin> (raw)
In-Reply-To: <234909.335371287999912985.JavaMail.root@mail-zbox20.bo3.lycos.com>
On Mon, 2010-10-25 at 05:45 -0400, Artem S. Tashkinov wrote:
[....]
> That's my point. "2.6" prefix is totally meaningless nowadays. I just
Only if you ignore the first 10(?) years of the Linux kernel.
> want to rejuvenate the numbering scheme and make it easy to understand
> and comprehend. What's the difference between .16 and .36? Besides, I
`diff -urN` will show. SCNR ...
What' the difference between 2010-3 and 2010-11?
Hooray, 8 months.
But what does that really tell us?
Nothing about the released item. And we loose the information if there
were other releases in between.
> just think these huge numbers look unsightly. Do you know any other
> piece of software which has the same huge numbers?
Yes, those that use years (and months) in their release numbering
scheme.
And no, because they release so often new "major" releases that they are
thus inherently unstable and buggy. SCNR ...
It makes absolutely no sense to use any version numbering (or naming) as
such as an indicator for anything - except *within the very same
project* to keep the releases in chronological order - both for humans
and software/scripts/tools/.....
Relying on release numbers for QA (or similar issues) is not a good
idea.
Bernd
--
Bernd Petrovitsch Email : bernd@petrovitsch.priv.at
LUGA : http://www.luga.at
next prev parent reply other threads:[~2010-10-25 10:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18536664.253751287691209904.JavaMail.root@mail-zbox20.bo3.lycos.com>
2010-10-21 20:02 ` On Linux numbering scheme Artem S. Tashkinov
2010-10-22 0:06 ` kevin granade
2010-10-22 2:00 ` Al Viro
2010-10-22 9:53 ` Athanasius
2010-10-22 17:36 ` Bill Davidsen
2010-10-22 21:57 ` Jeremy Fitzhardinge
2010-10-25 9:08 ` Tejun Heo
2010-10-25 9:45 ` Artem S. Tashkinov
2010-10-25 9:56 ` Tejun Heo
2010-10-25 10:04 ` Bernd Petrovitsch [this message]
2010-10-25 20:30 ` Nick Bowler
2010-10-26 10:24 ` Dick Streefland
2010-10-26 10:50 ` Martin Nybo Andersen
2011-01-06 8:31 ` Claudio Scordino
2011-01-06 8:59 ` Geert Uytterhoeven
2011-01-08 14:49 ` Artem S. Tashkinov
2011-01-08 16:11 ` Greg KH
2011-01-09 12:54 ` Mark Hounschell
[not found] <5600814.270321287742009359.JavaMail.root@mail-zbox20.bo3.lycos.com>
2010-10-22 10:33 ` Artem S. Tashkinov
2010-10-22 10:41 ` Alexey Dobriyan
2010-10-22 11:18 ` Artem S. Tashkinov
2010-10-22 13:25 ` Genes MailLists
2010-10-22 16:51 ` kevin granade
[not found] <18673709.2121294505029740.JavaMail.root@mail-zbox20.bo3.lycos.com>
2011-01-08 16:45 ` Artem S. Tashkinov
2011-01-08 18:31 ` Greg KH
2011-01-09 17:38 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1288001078.17570.24.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--cc=htejun@gmail.com \
--cc=kevin.granade@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=t.artem@lycos.com \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.