Date: Tue, 3 Sep 1996 16:53:06 -0400 From: "Frank E. Terhaar-Yonkers" <fty@mcnc.org> To: current@freebsd.org Subject: suggestion: Re: Latest Current build failure Message-ID: <199609032053.QAA25476@robin.mcnc.org>
next in thread | raw e-mail | index | archive | help
How about a simple status report? Like simply the CTM # and a one word status: "ng" (won't build), "builds" and "runs" (reasonably stable). One could then hold the CTM updates and only apply those up to a known stability point, waiting on those in-between. The field doesn't bleed so much, and current still gets a reasonable shake out. Snaps could be less frequent as well. - Frank Ollivier Robert Wrote: >To: current@freebsd.org >Subject: Re: Latest Current build failure > >According to Chuck Robey: >> I'm running ctm/cvs myself, and current has been incredibly stable. > >I don't want to add too much fuel to the discussion but I agree with Chuck >here. CURRENT is stable for me too. People who can't bear to have the tree >broken for a few hours without complaining should either stop running >CURRENT or provide a fix if they can't wait for the next sup/ctm. > >"Bleeding edge" has _bleeding_ in it. It seems that people tend to forget >that. I agree with Jordan that in an ideal world, it would be buildable at >any time but we live in a practical one; a few hic-hup are to be >expected. One should live with it or use only snapshots/releases... > >2 cts from a happy CURRENT user. >-- >Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr >FreeBSD keltia.freenix.fr 2.2-CURRENT #20: Fri Aug 30 23:00:02 MET DST 1996 > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609032053.QAA25476>