All of lore.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: Tue, 22 Jul 2008 12:30:13 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080722T120836-981@post.gmane.org> (raw)
In-Reply-To: alpine.DEB.1.10.0807210216260.1125@asgard.lang.hm

 <david <at> lang.hm> writes:


> you are well past the point where the complexity overwelmes the 
> information you are providing.
> 
> does it really matter _exactly_ when a release was made?
> 
> David Lang
> 
It might not really matter, but if you could find a reason for it to be useful,
then why not ?

As I wrote before, the development of the kernel is currently quite fast-paced.
The scale of changes is not that dramatic as it was in the early days, is it ?
Of course things get added, removed and so on. You even get lots of development
trees tested in linux-next on a daily basis. With date-based version number, you
can exactly position your own tree in time related to the current development.
It is more human-readable. The version number as it is, just does not entirely
fit the current model of development IMO - with 2 week merge window and roughly
2 months of stabilization period, the counter becomes sort of uninformative... 
But for the releases, the week-based granularity seems to be enough - the
current habit of having a stable by number is actually OK too, since the -stable
team does its job. So, yes, to have a similar version number to what is used
currently, the scheme could be s.yy.ww.[nn || -rcX], s=series (2), yy= year,
ww=week when the tree was released, nn= stable number. What do you think ?



  reply	other threads:[~2008-07-22 12:30 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
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 [this message]
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.20080722T120836-981@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 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.