Re: Staying *really stable* in FreeBSD

2001-06-27 Thread Jordan Hubbard
This looks really good! Ship that baby! :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message

Re: Staying *really stable* in FreeBSD

2001-06-27 Thread Gerhard Sittig
On Wed, Jun 27, 2001 at 13:13 -0600, Mike Porter wrote: > On Wednesday 27 June 2001 09:44, Bill Moran wrote: > > > > Is there a reason why you took this off the list? > > my mistake (or my mailer's depending on how you look at it). > If the majordomo config file for the list included the line > "

RE: Staying *really stable* in FreeBSD

2001-06-27 Thread Bill Moran
On Wednesday, June 27, 2001 5:30 PM, Juha Saarinen [SMTP:[EMAIL PROTECTED]] wrote: > On Wed, 27 Jun 2001, Bill Moran wrote: > > > In a company, alpha testing is done by the developers or other > > employees of the company, > > Once Upon A Time this was true, but no longer. Viz. Microsoft's > "Te

RE: Staying *really stable* in FreeBSD

2001-06-27 Thread Bill Moran
On Wednesday, June 27, 2001 3:14 PM, Mike Porter [SMTP:[EMAIL PROTECTED]] wrote: > On Wednesday 27 June 2001 09:44, Bill Moran wrote: > > Is there a reason why you took this off the list? > > > my mistake (or my mailer's depending on how you look at it). If the > majordomo config file for the li

RE: Staying *really stable* in FreeBSD

2001-06-27 Thread Juha Saarinen
On Wed, 27 Jun 2001, Bill Moran wrote: > In a company, alpha testing is done by the developers or other > employees of the company, Once Upon A Time this was true, but no longer. Viz. Microsoft's "Technology Preview" editions of various pieces of software. Due to lengthening development cycles,

Re: Staying *really stable* in FreeBSD

2001-06-27 Thread Juha Saarinen
On Tue, 26 Jun 2001, Nik Clayton wrote: > I've rewritten section 19.2.2.1 and 19.2.2.2 at > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html > > Do people think this gets the point across any better? Yep! It's now abundantly clear. -- Regards, Juha PGP fing

Re: Staying *really stable* in FreeBSD

2001-06-27 Thread Mike Porter
On Wednesday 27 June 2001 09:44, Bill Moran wrote: > Is there a reason why you took this off the list? > my mistake (or my mailer's depending on how you look at it). If the majordomo config file for the list included the line "reply-to: [EMAIL PROTECTED]" then all replies would by defualt go ba

Re: Staying *really stable* in FreeBSD

2001-06-27 Thread Nik Clayton
On Wed, Jun 27, 2001 at 09:41:18AM -0500, Christopher Schulte wrote: > > At 11:44 PM 6/26/2001 +0100, Nik Clayton wrote: > >I've rewritten section 19.2.2.1 and 19.2.2.2 at > > > > > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html > > > >Do people think this gets th

Re: Staying *really stable* in FreeBSD

2001-06-27 Thread Nik Clayton
On Sun, Jun 24, 2001 at 02:34:03AM -0700, Jordan Hubbard wrote: > From: "Juha Saarinen" <[EMAIL PROTECTED]> > Subject: RE: Staying *really stable* in FreeBSD > Date: Sun, 24 Jun 2001 12:00:59 +1200 > > > "19.2.2.2. Who needs FreeBSD-STABLE? > > If

RE: Staying *really stable* in FreeBSD

2001-06-27 Thread Bill Moran
Is there a reason why you took this off the list? On Wednesday, June 27, 2001 10:52 AM, Mike Porter [SMTP:[EMAIL PROTECTED]] wrote: > On Wednesday 27 June 2001 07:11, you wrote: > > On Tuesday, June 26, 2001 5:07 PM, Chad R. Larson [SMTP:[EMAIL PROTECTED]] > wrote: > > > If anyone is taking vot

Re: Staying *really stable* in FreeBSD

2001-06-25 Thread Joe Kelsey
Mike Porter writes: > [Lots of rambling ideas ...] First of all Mike, quite an interesting post. Unfortuantely, either the author of the book didn't understand or didn't explain the CMM well enough for you to be able to use it. I have worked as a Software Quality Engineer (really doing Quality,

RE: Staying *really stable* in FreeBSD

2001-06-25 Thread Jason Watkins
I think it's become clear in this discussion that some people reguard -stable as the secure, regularly updated moving release canidate. Other people view -stable as a just stable enough branch for developers to coordinate building new functionality. If the 2nd view is the official one, then a new

RE: Staying *really stable* in FreeBSD

2001-06-25 Thread Jason Watkins
JK> All of your problems can be traced back to old hardware or inexperience with the latest thinking in BSD land. Because you have not upgraded your 2.x system, you are essentially stuck. Either get newer hardware to work with or go through the upgrade based on your subscription disks. While th

RE: Staying *really stable* in FreeBSD

2001-06-25 Thread Jason Watkins
JW> I react rather badly to some of your comments concerning the usability of JW> FreeBSD. Our goal *should* be a simple and turnkey system, or at the least, SH> That would be a RELEASE. They are usually pretty good at being just that IMHO. No, usability follows from design and functionality. T

Re: Staying *really stable* in FreeBSD

2001-06-24 Thread Adrian Wontroba
On Fri, Jun 22, 2001 at 11:54:10PM -0400, Kevin Way wrote: > cvsup works fine over dialup, and not unacceptably slowly either. I cvsup the whole thing, maintaining my own local copy of the entire repository. Source, ports, doc, gnats, www. No refuse files at all (not got round to it). I norma

Re: Staying *really stable* in FreeBSD

2001-06-23 Thread Steve O'Hara-Smith
On Sun, 24 Jun 2001 12:00:59 +1200 "Juha Saarinen" <[EMAIL PROTECTED]> wrote: JS> :: The tracking of stable is not for everyone. Noone *needs* to track JS> :: stable. JS> JS> Well, that isn't what the Handbook says: JS> JS> "19.2.2.2. Who needs FreeBSD-STABLE? JS> If you are a commercial use

Re: Staying *really stable* in FreeBSD

2001-06-23 Thread mome-rath
On Sun, Jun 24, 2001 at 02:45:24AM +0200, Michael Nottebrock wrote: > > You make some very good points. For you, like 99% of Linux users, you > > are better off never attempting to cvsup or to track stable. > > [...] > > I just like to say that my experience with tracking stable is quite > pos

RE: Staying *really stable* in FreeBSD

2001-06-23 Thread Mike Meyer
FreeBSD Admin <[EMAIL PROTECTED]> types: > I haven't posting anything in some time, so I'm making up for it now with > this tome. 8-) It says nothing important and means nothing, so skip as you > like. You do have some very good points, and some of them are being addressed already. > Don't thi

Re: Staying *really stable* in FreeBSD

2001-06-22 Thread Mike Meyer
Dmitry Karasik <[EMAIL PROTECTED]> types: > On 21 Jun 01 at 16:45, "Jason" (Jason Watkins) wrote: > Jason> Don't camoflage one problem by providing a solution to > Jason> another. What you're really worried about is how stable -stable > Jason> is. Address that, and things will be better than ma

Re: Staying *really stable* in FreeBSD

2001-06-22 Thread David A. Panariti
Ok, last try. I'm not trying to push responsibility off on anyone. There will be in infinitesmal amount of work involved. The tag points to the RELENG_X_Y tag with the highest X primarily and the highest Y secondarily. That's it. No more. If someone has decided to create a new RELENG_X_Y then n

RE: Staying *really stable* in FreeBSD

2001-06-21 Thread Jason Watkins
And this would be different than -stable how? >> Then we (paranoid and lazy types) can just cvsup that tag without >> needing to change from RELENG_X_Y to RELENG_X_Y+1 and RELENG_X+1_0. Don't camoflage one problem by providing a solution to another. What you're really worried about is how stable

Re: Staying *really stable* in FreeBSD

2001-06-21 Thread David A. Panariti
*not* editing the file) 4) ci -u supfile when I can do: nothing. This is easier, and less prone to mistakes. Given these two lists, Occam's razor would, I think, select the zero length list as the simpler one. Regards, davep Valentin> Thu, Jun 21, 2001 at 16:20:15, davep (David A. Pan