From owner-freebsd-advocacy Fri Aug 20 9: 6:57 1999 Delivered-To: freebsd-advocacy@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 794B31534F for ; Fri, 20 Aug 1999 09:06:54 -0700 (PDT) (envelope-from will@shadow.blackdawn.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=shadow.blackdawn.com) by neptune.psn.net with esmtp (PSN Internet Service 2.12 #3) id 11HrBL-0004mb-00; Fri, 20 Aug 1999 09:06:20 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.2) id MAA11197; Fri, 20 Aug 1999 12:06:16 -0400 (EDT) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990820084318.A48102@voodoo.pandhm.co.uk> Date: Fri, 20 Aug 1999 12:06:15 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: Dominic Mitchell Subject: Re: -CURRENT mentioned on Freshmeat Cc: advocacy@FreeBSD.ORG Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Aug-99 Dominic Mitchell wrote: > On the otherhand, it's not explicitly listed as "This is -CURRENT, not a > release. In fact it's just a daily snapshot"... Indeed, it's not. This could lead to folks simply downloading FreeBSD 4.0-CURRENT because it was advertised on freshmeat and then finding out that their computer doesn't even boot because of some problem with a new 4.0-CURRENT feature. Then, thanks to freshmeat, we might actually lose the prospect of a new FreeBSD user. However, it would be VERY nice (IMO) if freshmeat announced 3.3-RELEASE later this year. THEN users would be on a polished FreeBSD OS (certainly we could lose them for another reason, but that's not the issue here ;). -- Will Andrews To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message