From owner-freebsd-current@FreeBSD.ORG Sun Jul 3 09:44:10 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0734116A41C for ; Sun, 3 Jul 2005 09:44:10 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99FE643D45 for ; Sun, 3 Jul 2005 09:44:09 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A54C8.dip.t-dialin.net [84.154.84.200]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j639i68o086492; Sun, 3 Jul 2005 11:44:07 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j639i3V7001481; Sun, 3 Jul 2005 11:44:06 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.3) with ESMTP id j639i3Gc052506; Sun, 3 Jul 2005 11:44:03 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200507030944.j639i3Gc052506@fire.jhs.private> To: Chuck Swiger In-Reply-To: Message from Chuck Swiger of "Wed, 30 Mar 2005 11:43:49 CDT." <424AD745.2040402@mac.com> Date: Sun, 03 Jul 2005 11:44:03 +0200 From: "Julian H. Stacey" Cc: freebsd-current@freebsd.org Subject: Re: freebsd naming of releases X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jul 2005 09:44:10 -0000 HEADS UP Below is a repeat posting dated Wed, 30 Mar 2005. I'm not convinced Chuck re-posted it, as I think I've read it before. I've forwarded to postmasters to investigate. The thread was debated to termination back then, & deosn't need revival now. It might be a troll trying to blow air on embers, or it might be a bad config somewhere, but hopefully all except investigating postmasters, (particularly @mu.org) can ignore it. Thanks -- Julian Stacey Muenchner Unix Urlaubs Vertretungs Dienst http://berklix.com Mail in Ascii (Html = Spam). Ihr Rauch = mein allergischer Kopfschmerz. -------- Chuck Swiger wrote: > Julian H. Stacey wrote: > > Charles Swiger wrote: > >>>I find that the terms "alpha", "beta" and "production" do not quite > >>>fit the FreeBSD development paradigm. (Is RELENG_5 beta or > >>>production?) > >> > >>It's beta. -CURRENT (or RELENG_6) is alpha, and production is now at > > > > > > Wrong: Current != Alpha. > > Industry common parlance of "Alpha Release" is per se a sort of (pre) release. > > FreeBSD Current is continuously moving & not a release; eg cvs -r HEAD > > I know that HEAD is continuously moving. Saying code is "in alpha" does not > imply that it is ready for release or being put through a release cycle. > > I suppose that someone comfortable with the term "alpha release" would also be > happy with the notion of "paid beta releases": software made publicly > available to all customers (which is my definition of "going into production", > or perhaps "going into production but trying to avoid providing real support > even if people have paid for the software" is closer :-). > > > Perhaps you equated Alpha & Current because that's the first one > > has access to from commercial companies & FreeBSD respectively, but > > that doesnt make them the same thing. Binaries from a commercial > > company's current one wouldn't normally see (let alone the source :-). > > No, my definition of alpha means "code that works well enough to implement at > least some major features, but may be missing other features and is expected > to contain significant bugs which make it unwise to depend on the system for > production use". Windows jokes aside, commercial companies don't normally > release alpha code to the outside world. > > Beta means "code that is basicly feature-complete modulo bugs, is ready for > outside testing, but still contains significant bugs and is not guaranteed to > be stable for production" (as in, "beta code is not supported"). > > In FreeBSD, one critereon for whether a release is in production, is whether a > security advisory results in that branch being updated. The recent release of > FreeBSD-SA-05:01.telnet resulted in RELENG_5_3, RELENG_4_11, and RELENG_4_10 > being updated as well as HEAD, RELENG_5, & RELENG_4. (Maybe 4.8, too.) > > -- > -Chuck > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > -- Julian Stacey Consultant Systems Engineer, Munich. http://berklix.com Mail in Ascii (Html = Spam). Ihr Rauch = mein allergischer Kopfschmerz.