From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263810AbTK2QvB (ORCPT ); Sat, 29 Nov 2003 11:51:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263811AbTK2QvB (ORCPT ); Sat, 29 Nov 2003 11:51:01 -0500 Received: from h192n2fls310o1003.telia.com ([81.224.187.192]:14976 "EHLO cambrant.com") by vger.kernel.org with ESMTP id S263810AbTK2Qu7 (ORCPT ); Sat, 29 Nov 2003 11:50:59 -0500 Date: Sat, 29 Nov 2003 18:49:16 +0100 From: Tim Cambrant To: Linux Kernel Mailing List Subject: Too soon for stable release? Message-ID: <20031129174916.GA4592@cambrant.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I am sorry if this offends someone or if I'm totally on the wrong track here, but it seems odd to actually call the Beaver On Detox "stable", considering the amount of misc. problems people have been having the last week with -test11. Since you are in schedule, a -test12 with the bugs fixed might be a better idea, don't you think? Since I'm not a coder, and havn't had any previous kernel development experince, I might not be the one to suggest such a thing, but I really don't see a reason to be hasty with the release, and end up with a whole bunch of users having problems. The weeks Linus suggested we would wait before releasing the final 2.6.0-kernel could be a perfect time to implement the fixes that would be needed. Test11 is working perfectly for me, but you can clearly see that many people are having problems. -- Tim Cambrant GPG KeyID 0x59518702 Fingerprint: 14FE 03AE C2D1 072A 87D0 BC4D FA9E 02D8 5951 8702