From owner-freebsd-questions@FreeBSD.ORG Sat Jan 21 15:59:04 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 337B016A41F for ; Sat, 21 Jan 2006 15:59:04 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A25A43D4C for ; Sat, 21 Jan 2006 15:59:02 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (patr530b-0071.otenet.gr [62.103.226.71]) by kane.otenet.gr (8.13.4/8.13.4/Debian-8) with ESMTP id k0LFwxu8014007; Sat, 21 Jan 2006 17:59:00 +0200 Received: by flame.pc (Postfix, from userid 1001) id 5AFBE118D4; Sat, 21 Jan 2006 17:36:30 +0200 (EET) Date: Sat, 21 Jan 2006 17:36:30 +0200 From: Giorgos Keramidas To: Nikolas Britton Message-ID: <20060121153630.GA1797@flame.pc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-questions@freebsd.org Subject: Re: Best time of day/week to cvsup? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2006 15:59:04 -0000 On 2006-01-21 02:30, Nikolas Britton wrote: > For example, what time of day, and the day of the week, is typically > the best time to sync up with 6-STABLE or 7-CURRENT, to minimize > dealing with untested new commits. CURRENT is, by definition, a fair bit unpredictable. Unless, of course you track freebsd commits and freebsd-current. But even then, updating is not always `safe' -- for some definition of `safe'. For instance, after the update of malloc() by Jason Evans to his new, improved version, many programs started crashing in 7.0-CURRENT because of bugs in those programs. I usually try to keep up with the mail of freebsd-cvs-src and the posts of freebsd-current and update my systems manually to 7.0-CURRENT when I'm relatively sure that things are `stable enough' for my work. Having said that about CURRENT, I'm sure that 6.0-STABLE is quite safe most of the time, because changes don't just get rushed in to the RELENG_6 branch. Not having a steady stream of commits flowing in means that most of the time CVSUP'ing a 6-STABLE system will pull in changes to manpages, system documentation and the occasional security fix. So, it's much safer to pick any random time and update a RELENG_6 system. > Same goes for the ports system. Are there any cvs usage stats or web > server usage stats for the FreeBSD project? > > I'd like to setup an automated package building system for 6.0-RELEASE > and 6-STABE. Colin Percival does this already for `security/freebsd-update'. He may have many good ideas to share, so you should definitely try to contact him :)