public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael C. de Almeida" <almeidaraf@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: From 2.4 to 2.6 to 2.7?
Date: Wed, 16 Jul 2008 03:55:20 -0300	[thread overview]
Message-ID: <487D9B58.7070609@gmail.com> (raw)
In-Reply-To: <487D7781.6000407@keyaccess.nl>

Rene Herman wrote:
> On 15-07-08 20:04, H. Peter Anvin wrote:
> 
>> Clearly, the 2. prefix has long outlived its usefulness as far as
>> Linux is concerned, and probably the 6 as well.
> 
> Been calling the -stable branches v20, v21, v22, ... here.
> 
> I do believe the numbering scheme should at least ostensibly still be
> feature driven, not be a fully robotic date thing. With the latter, you
> definitely miss out on press-opportunities and that's not even meant
> cynical. There just is a bit of industry around Linux and the promotion
> opportunities of (say) "Linux 3" are really lots, lots bigger than
> anything boringly date based.

And that's why after the adoption of generics and a few things java all
the sudden became java 5. I don't like that. I hope the world gets used
to learning things instead of just being driven by a pretty number. And
I think that not using marketing numbers on a popular software is a good
step into helping people realise that version numbers are meant to keep
track of the changes not to look cool.

> That even holds for things like books -- I just bet that a "all new,
> covers Linux 3!" blurp on the cover sells lots more copies than a "all
> new, covers the march 21st 2009 version of Linux!" one.

I rather just have good books around. I can bet that all -- or at least
most of -- those new "LINUX 3!" books would suck. So it's better if they
sell little or not sell at all.

> But yes, the current monotic increase is definitely getting a bit boring
> as well. The kernel as of 2.6.26 is quite different from the kernel that
> was known as 2.6.0 so just be creative I'd say and set a 2.8 goal. Next
> version can be 2.9 (should be clear enough by then) and then watch world
> domination happen with the big 3.0 release.

Well, if 2.6.0 was 3.0 (2003.0) then people would easily realise that
they're missing 5 years of kernel development. Given that hint, if they
take a look on a few Changelogs they'll soon find out they're missing on
quite a lot.

> Linux 2010.5? Boooooooooring....

Well, it is software versioning and not Gisele Bündchen taking off her top.

> Rene.

  reply	other threads:[~2008-07-16  6:55 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  2:10 From 2.4 to 2.6 to 2.7? 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
2008-07-15 18:04   ` H. Peter Anvin
2008-07-16  4:22     ` Rene Herman
2008-07-16  6:55       ` Rafael C. de Almeida [this message]
2008-07-16  7:17         ` Rene Herman
2008-07-16  7:30         ` Rene Herman
2008-07-16  9:34       ` Peter T. Breuer
  -- strict thread matches above, loose matches on Subject: below --
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=487D9B58.7070609@gmail.com \
    --to=almeidaraf@gmail.com \
    --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