linux-kernel - Re: Kernel version : what about s.yy.ww.tt scheme ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <loom.20080718T075647-205@post.gmane.org>
Date:	Fri, 18 Jul 2008 08:31:48 +0000 (UTC)
From:	el es <el_es_cr@...oo.co.uk>
To:	linux-kernel@...r.kernel.org
Subject:  Re: Kernel version : what about s.yy.ww.tt scheme ?

 <david <at> lang.hm> writes:

> 
> it means that you cannot know what version of the kernel you are getting 
> ready to release.

Yes, but when it is at large, everybody would know at a first glance, when it
was released.

> 
> today we can talk that we are working on 2.6.27 or 'this feature was 
> accepted and will be in 2.6.27' any scheme that uses the date of the 
> release means that we can't do this.
> 

With current scheme you say 'it will be in next stable mainline', not telling
any predictions when will it happen, as the stable number is only an increment,
not bound to anything but the cycle. Which many people do not understand and/or
do not want to. My numbering is not the date of _projected_ release, but the
actual date (week) when the release happened. And then, the actual week when the
stable hit large.

> I see this as a big problem with a fine-grained date scheme.
> 
> if we use the year in a date-based scheme and have a near end-of-year 
> release slip into the next year (2008.4 is released in Jan 2009) I don't 
> see this as a major problem (the bulk of the work was done in 2008 even if 
> the final release hit in 2009) under the current development cycle it's 
> not like this will end up with 'version 2009.2 released in 2011' type 
> emberrasements.

Yes, my numbering addresses this issue. It is the actual date of release,
encoded week-wise. Any development that is not expected to be 'stable' happens
in 2.mm.ww-rcX where ww is the _last_ stable mainline, frozen. Then, at first
glance you can tell 'Oh, your tree is 3 months older than mine, please rebase
before I pull it' or 'Oh, I need to rebase my tree 'cause I haven't done that
for 4 months' sort of things. Even the automated tools have it easier to tell
you when you push a tree 'Your tree is soooo out of date. Do you really want to
push your stale code to somebody else ?' or 'That tree you're pulling, was last
rebased on code created last year. You sure you want it ?'. Just hypothetically.

> 
> David Lang
> 

el es
[the 'what' in the topic is a thinko, but I don't want to spoil the thread]

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/