From owner-freebsd-stable Mon Jun 11 16:32:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snoop.burghcom.com (burgcom.cust.stargate.net [209.166.166.21]) by hub.freebsd.org (Postfix) with SMTP id 27C8537B401 for ; Mon, 11 Jun 2001 16:32:34 -0700 (PDT) (envelope-from jl@burghcom.com) Received: (qmail 52670 invoked from network); 11 Jun 2001 23:32:33 -0000 Received: from host207.64-31-3.bignet.net (HELO gate) (64.31.3.207) by snoop.burghcom.com with SMTP; 11 Jun 2001 23:32:33 -0000 Message-ID: <00a201c0f2ce$c955c4c0$010aa8c0@burgh.net> From: "Jeff Love" To: References: <20010611172443.A18552@home.com> Subject: Re: Why is the STABLE branch not so stable anymore? Date: Mon, 11 Jun 2001 19:32:31 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I run a test server comparable to my production server. I ALWAYS test my upgrades on the test server before compiling the same src in production. IMHO, it would be quite foolish to do otherwise. Jeff Love Burgh-Com ----- Original Message ----- From: "Mixtim" To: Sent: Monday, June 11, 2001 5:24 PM Subject: Why is the STABLE branch not so stable anymore? > Several times in the last few weeks people have broken the STABLE branch, > sometimes for days at a time. Why has this started happening? Is there no > process to prevent this from happening? > > I have a wild idea. How about making everyone who commits to the STABLE > branch actually: > > 1. Checkout a clean copy. > 2. make buildworld. > 3. Actually test the programs they changed. > > These three steps would have prevented each of the problems in the last few > weeks. Does no one test anymore? Is no one required to test? > > Perhaps a process should be put into place. (unless there already is one in > which case someone should start cracking the whip over some backs). > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message