From: Tobias Brox <tobias@stud.cs.uit.no>
To: linux-kernel@vger.kernel.org
Subject: Re: From 2.4 to 2.6 to 2.7?
Date: Tue, 15 Jul 2008 18:36:52 +0200 [thread overview]
Message-ID: <20080715163652.GA12728@lgserv3.stud.cs.uit.no> (raw)
In-Reply-To: <20080715142444.GA7121@asus>
[Cyrill Gorcunov]
> Some areas should be distinguished:
Areas? "Target audience groups" maybe? Well, I'm also not a native
English writer ;-)
> - development/stable team
> - distros
> - regular users
> So we have the quite large group of people which should be considered for
> convenient versioning scheme - _regular users_. Lets say I'm a regular user -
> the most convenient scheme for me would be YYYY.r.s i think since it tells
> me - this kernel is fresh enough to be used on my shining laptop, and maybe
> it even supports all hardware I have! And at least it looks good -
> Linux-2008.0.0
So, the version numbers aren't important for anyone else than "regular
users"? Ok, I'm a "regular user", so then I'm qualified to comment
;-)
Microsoft has attempted using year numbers in their releases, do we
really want to go the same way? ;-) Well, indeed - my vote goes in the
direction of YYYY.r.s. I have one concern though, such a release
could easily be mistaken for beeing an actual date. Maybe better to
write 2008.r1.s1 to make it explicit it isn't the release date?
2008.r1.s1 would at a glance easily give me an impression on whether
the kernel version is "outdated", "mature" or "fresh". 2008.r1.s1 is
easily googlable (though googling for "linux changelog 2.6.25" isn't
really that difficult)
That being said, is it really reasonable to assume the linux kernel
will continue evolving gradually for all future? In all software,
sometimes it is really needed to make some major changes, break
backward compatibility and decrease the stability - and that's what
the major version numbers are for. I think saying "we'll never need
to change the major version number again" is roughly equivalent with
"the design of Linux 2.6 is perfect". Or, maybe some years or decades
down the road we'll all upgrade to something with a different name
than Linux ;-)
--
Tobias Brox, 69°42'N, 18°57'E
next prev parent reply other threads:[~2008-07-15 16:43 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 2:10 Stoyan Gaydarov
2008-07-15 2:22 ` Linus Torvalds
2008-07-15 2:31 ` Stoyan Gaydarov
2008-07-15 2:47 ` Linus Torvalds
2008-07-15 3:55 ` david
2008-07-15 5:31 ` Willy Tarreau
2008-07-15 6:40 ` Rafael C. de Almeida
2008-07-15 7:23 ` Stoyan Gaydarov
2008-07-15 7:49 ` Jan Engelhardt
2008-07-17 17:25 ` Jan Engelhardt
2008-07-17 19:56 ` Craig Milo Rogers
2008-07-17 20:21 ` Jan Engelhardt
2008-07-19 8:00 ` Craig Milo Rogers
2008-07-19 8:52 ` Rene Herman
2008-07-19 20:49 ` Craig Milo Rogers
2008-07-19 20:56 ` david
2008-07-19 21:56 ` Jan Engelhardt
2008-07-20 8:34 ` Rene Herman
2008-07-20 14:53 ` Stefanos Harhalakis
2008-07-19 19:30 ` Peter T. Breuer
2008-07-19 21:16 ` Craig Milo Rogers
2008-07-19 23:10 ` Peter T. Breuer
2008-07-15 8:29 ` Bernd Petrovitsch
2008-07-15 12:41 ` Kasper Sandberg
2008-07-15 13:18 ` Alberto Gonzalez
2008-07-15 18:06 ` Charles grey wolf Banas
2008-07-15 20:43 ` Adrian Bunk
2008-07-16 7:53 ` Jan Engelhardt
2008-07-16 7:57 ` Rene Herman
2008-07-17 22:16 ` Adrian Bunk
2008-07-15 10:10 ` Andi Kleen
2008-07-15 11:31 ` Jan Engelhardt
2008-07-15 15:20 ` Linus Torvalds
2008-07-15 15:27 ` Parag Warudkar
2008-07-15 15:32 ` Alan Cox
2008-07-18 9:02 ` Andi Kleen
2008-07-16 21:11 ` Lennart Sorensen
2008-07-15 12:38 ` Alan Cox
2008-07-15 14:07 ` Byron Stanoszek
2008-07-16 21:14 ` Lennart Sorensen
2008-07-17 0:03 ` Alex Chiang
2008-07-17 12:38 ` Lennart Sorensen
2008-07-17 20:02 ` Alex Chiang
2008-07-15 14:24 ` Cyrill Gorcunov
2008-07-15 16:36 ` Tobias Brox [this message]
2008-07-15 18:04 ` H. Peter Anvin
2008-07-16 4:22 ` Rene Herman
2008-07-16 6:55 ` Rafael C. de Almeida
2008-07-16 7:17 ` Rene Herman
2008-07-16 7:30 ` Rene Herman
2008-07-16 9:34 ` Peter T. Breuer
2008-07-17 22:05 Alastair Stevens
2008-07-17 22:40 ` Lennart Sorensen
2008-07-18 8:23 ` Peter T. Breuer
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=20080715163652.GA12728@lgserv3.stud.cs.uit.no \
--to=tobias@stud.cs.uit.no \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®