Date: Mon, 8 Nov 2004 11:53:56 -0500 (EST) From: Jerry McAllister <jerrymc@clunix.cl.msu.edu> To: TM4526@aol.com Cc: questions@freebsd.org Subject: Re: difference between releases Message-ID: <200411081653.iA8GrvA06681@clunix.cl.msu.edu> In-Reply-To: <d4.1a9c2a60.2ec0fd0a@aol.com> from "TM4526@aol.com" at Nov 08, 2004 11:47:06 AM
next in thread | previous in thread | raw e-mail | index | archive | help
> > In a message dated 11/8/04 10:49:14 AM Eastern Standard Time, > keramida@ceid.upatras.gr writes: > >> How discouraging for you not to understand that. > > > > Its "discouraging", because a "Release" should be " a completed set of > > features that have been tested and thought to be bug-free" > > >You know that this isn't exactly true. I have yet to see one "release" of > any > >product that does not have bugs. I probably never will. > > I think the "thought to be bug-free" covers that, but I know that english is > a > difficult language. > > The problem with "getting over it" is that people "think" that a release is > thought > to be well-tested, but its apparently no different from any other beta > release. > > I think its rather important. When you get a release, you don't expect that > some unknown set of features is still in some sort of Beta stage. The purpose > of a release is to get what you're doing done, and then start on new stuff > based > on the "release", which should be a known, completed code base. > > All part of the experience I suppose. The whole world is in beta. Get over it. ////jerry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200411081653.iA8GrvA06681>