From owner-freebsd-stable Wed Dec 8 13:21: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from puffer.quadrunner.com (puffer.quadrunner.com [205.166.195.4]) by hub.freebsd.org (Postfix) with ESMTP id 91EA515670 for ; Wed, 8 Dec 1999 13:20:53 -0800 (PST) (envelope-from manek@ecst.csuchico.edu) Received: from after (root@puffer.quadrunner.com [205.166.195.4]) by puffer.quadrunner.com (8.9.2/QUAD-2.1) with SMTP id NAA08023; Wed, 8 Dec 1999 13:19:34 -0800 (PST) From: "Sameer R. Manek" To: "Jose Marques" , Subject: RE: 3.2 -> 3.3-stable Date: Wed, 8 Dec 1999 13:20:47 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Jose Marques > Sent: Wednesday, December 08, 1999 11:57 AM > > I would like to use CVSup to bring a machine currently running FreeBSD > 3.2-RELEASE up to 3.3-stable. Are there any "gotchas" that I should be > aware of? Biggest one would be if you cvsup tonight, you'll jump to 3.4-RC. 3.4-RC is a release canidate, aka beta for 3.4-RELEASE. You might want to wait until 3.4-RELEASE, the source tree can get a little unstable just before -RELEASE, as the developers scramble to get patches commited before the code freeze. 3.4-RELEASE is scheduled to come out right around the same time Santa does, so might as well wait a few days, and have some eggnog. Sameer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message