lkml.org 
[lkml]   [1997]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.0.31 : please!
On Thu, 17 Jul 1997, Theodore Y. Ts'o wrote:

> I don't know the solution. Maybe new stable kernel revisions should be
> dubbed 'beta' versions, the 'beta' being removed when the kernel
> proves to be stable in public usage for a few weeks. Maybe never
> releasing a new version without a plethora of pre-patches is it. Or
> even re-releasing 2.0.29 as 2.0.31 and 2.0.30-pre2 as 2.0.32-pre, thus
> removing 2.0.30 from the 'market' solves the problem for now.
>
> You're assuming that people will use the the beta versions. (Instead of
> being spoiled brats who don't do anything and just complain, complain,
> commplain.....) We already have the 2.0.30-pre2 release; if people
> don't test it with the name 2.0.30-pre2, will changing the name help?

2.0.30-pre2 is not in the "expected" place in the kernel mirrors. Unless
people know to look in the davem dir or on vger, they won't find it.
Those who just look in kernel/v2.0 to find the "latest stable" kernel
won't know about it. Maybe it should be moved into kernel/v2.0 or at
least the LATEST-IS-2.0.30 could be traded for LATEST-IS-2.0.31-pre2.

------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
________Finger jlewis@inorganic5.fdt.net for PGP public key_______


\
 
 \ /
  Last update: 2005-03-22 13:39    [W:0.040 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site