From owner-freebsd-current Mon Feb 19 8:54:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A801E37B503 for ; Mon, 19 Feb 2001 08:54:12 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) id f1JGsA189888 for freebsd-current@FreeBSD.ORG.AVP; Mon, 19 Feb 2001 17:54:10 +0100 (CET) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) with UUCP id f1JGsAq89882 for freebsd-current@FreeBSD.ORG; Mon, 19 Feb 2001 17:54:10 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.1/8.11.0) with SMTP id f1JGrvx71268 for ; Mon, 19 Feb 2001 17:54:03 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <00d001c09a94$b280d9c0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" Cc: References: <20010216025147.A25002@dragon.nuxi.com> <20010216104409.A99749@enigma.whacky.net> <20010216025147.A25002@dragon.nuxi.com> <200102161703.f1GH37E29782@billy-club.village.org> <20010217101500.A10023@enigma.whacky.net> Subject: Do we need a 3. level between stable and cuurent? Date: Mon, 19 Feb 2001 17:54:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by ns.internet.dk id f1JGsAq89882 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We all know: -current is bleeding edge, expect it to break at random. Don't run it if you don't know how to fix it. -stable is for production, it works all the time. Do we need a level in between for people who just run current for the fun of it and for testing. So after the hardcore has tested it in -current, they commit it to all the monkeys trying to break it, and we then try it on n^m' combinations of hardware/software. I might not be able to fix a problem, but I can report what happens, and if my -current breaks for a few days, it is no big deal. While -current is not for everybody, I believe people like me helps in quality testing before the stuff hits -stable. Perhaps not a level, just a separate file, which contained the date of the last known version without known major problems. (or "." if no known problems) Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message