public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: el es <el_es_cr@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel version : what about s.yy.ww.tt scheme ?
Date: Thu, 17 Jul 2008 10:38:32 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080717T100809-415@post.gmane.org> (raw)
In-Reply-To: alpine.LNX.1.10.0807171140030.18697@fbirervta.pbzchgretzou.qr

Jan Engelhardt <jengelh <at> medozas.de> writes:

> >The scheme to be s.yy.ww.tt, that is :
> >
> >s - series, as it is now (freedom to Linus to bump it to 3 when BKL is removed
> >for example ;) )
> >yy - two (in a hundred years, three) digits of the year
> >Now the interesting part begins which is
> >ww - the number of the week of the release. This will be between 1 and 52 (53)
> >tt - the number of the week of stable release. As above.
> 
> Interesting idea.
> 

Thanks :)

> -stable usually overlaps with master. But I don't like version
> numbers long as binutils and "2.8.30.9.01" have.

Yes, master and stable accumulate the same patches, I know. Only master takes
new code, whereas -stable does not.

This however tells how long did it take to produce the -stable release out of
Linus's release ;) And it does not break the current habits - just abuses them a
bit ;) 
And tells you how long the version was around there without another -stable
release too. Just by looking onto the version string, quick, sortable in
meaningful way, all sorts of pluses there ;)

IMO, the kernel is so mature already, and the development is so fast, and the
changes not always so fundamental, that the version in the old sense becomes
irrelevant - it is not the 2.4->2.6 transition days any more ;) 



Regards,
Lukasz (btw sorry I forgot to sign myself last time ;)




  reply	other threads:[~2008-07-17 10:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  8:51 Kernel version : what about s.yy.ww.tt scheme ? el es
2008-07-17  9:48 ` Jan Engelhardt
2008-07-17 10:38   ` el es [this message]
2008-07-17 14:27     ` Justin Mattock
2008-07-18  9:12       ` Jan Engelhardt
2008-07-18 16:24         ` Justin Mattock
2008-07-20 18:14   ` Willy Tarreau
2008-07-21  7:57     ` el es
2008-07-21  9:18       ` david
2008-07-22 12:30         ` el es
2008-07-17 23:02 ` david
2008-07-18  8:31   ` el es
2008-07-18 15:24   ` Kernel version : what about YYYY.MM.[01].x ? Athanasius
2008-07-22 15:18     ` el es

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=loom.20080717T100809-415@post.gmane.org \
    --to=el_es_cr@yahoo.co.uk \
    --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