From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 01:01:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BED637B401 for ; Mon, 18 Aug 2003 01:01:55 -0700 (PDT) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03DB143FA3 for ; Mon, 18 Aug 2003 01:01:55 -0700 (PDT) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (failways.internal [10.236.150.2]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 97A896A; Mon, 18 Aug 2003 10:02:56 +0200 (CEST) Date: Mon, 18 Aug 2003 10:01:44 +0200 (CEST) From: Alban Hertroys To: "Brandon S. Allbery KF8NH" In-Reply-To: <200308162108.58631.allbery@ece.cmu.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20030818080256.97A896A@solfertje.student.utwente.nl> cc: stable@freebsd.org Subject: Re: whining about tinderbox messages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Alban Hertroys List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 08:01:55 -0000 On 16 Aug, Brandon S. Allbery KF8NH punched keys in this particular order: > On the other hand, they do let you know (once the tinderbox has stabilized, > this being a new setup with the bugs being worked out of it) whether recent > -STABLE will build or not, which can be quite useful even for ordinary users > of -STABLE. (You know to hold off on updating if it's failing for your > platform(s).) Maybe you (or who else is responsible) can spare us the false and the excpected negatives, so that it looks at least like a trustworthy attempt? I don't consider it wise to send TB messages when you're not certain whether it is FreeBSD's fault or the tinderbox's. I also think it would be nicer to send a TB message at the first breakage, and a "builds again" message once the problems are solved. It is easier on the users like me, and I'm quite certain it's less annoying to the developers ("yeah yeah, I know that's broken, I'm working on it!"). And as a final remark; Could you please limit your opinion to the technical content, and exclude the people from it (referring to the subject)? Otherwise you're working to make a "mild annoyance" grow to a flamewar. And nobody wants that. -- Alban Hertroys http://solfertje.student.utwente.nl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I think, therefore I drink. - Lazarus -