public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: el es <el_es_cr@yahoo.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: Kernel version : what about s.yy.ww.tt scheme ?
Date: Sun, 20 Jul 2008 20:14:26 +0200	[thread overview]
Message-ID: <20080720181426.GA29189@1wt.eu> (raw)
In-Reply-To: <alpine.LNX.1.10.0807171140030.18697@fbirervta.pbzchgretzou.qr>

On Thu, Jul 17, 2008 at 11:48:37AM +0200, Jan Engelhardt wrote:
> 
> On Thursday 2008-07-17 10:51, el es wrote:
> 
> >Hello,
> >inspired by the bikeshed painting contest, I got the following idea :
> >
> >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.
> 
> >Take a hypotetical new-scheme 2.8.30 release (roughly the current
> >2.6.26, didn't count these weeks). Linus starts to accumulate
> >patches for 2.8.30-rcX as usual, and when he is ready to release,
> >puts the release week number instead of 30 - let's assume it is a
> >2.8.40 then, more or less. By the time, the stable team produces
> >2.8.30.[32,34,36,38,40 and so on]. If the weeks leap into the next
> >year, stable team puts e.g. 2.8.30.9.01 (yy.ww).
> 
> -stable usually overlaps with master. But I don't like version
> numbers long as binutils and "2.8.30.9.01" have.

also, causes trouble when stable releases cross a year boundary, or
when there are several ones in a week. The stable release should
only be a counter, not a date.

Willy


  parent reply	other threads:[~2008-07-20 18:14 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 [this message]
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=20080720181426.GA29189@1wt.eu \
    --to=w@1wt.eu \
    --cc=el_es_cr@yahoo.co.uk \
    --cc=jengelh@medozas.de \
    --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