From owner-freebsd-x11@FreeBSD.ORG Tue Oct 1 19:16:10 2013 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4FFC6F1C; Tue, 1 Oct 2013 19:16:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1F6C12150; Tue, 1 Oct 2013 19:16:10 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id w10so7702777pde.37 for ; Tue, 01 Oct 2013 12:16:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PfiZJoRpr4ZoafKFo1HwgiA57Q0sbCMUY6aJx/eQ5/8=; b=pjUfrrARi8+IJqRei0U8fBE9T9U5CQ6gNwxaPE4cv1UWsxB/CmfQRMjVmIXNYek0SB 2ODxglODuzi0LLwnqi2omNfWV8DaXwbHepjwGSE51k1rOP8u22Ar9RnIlO08acJ0P9td oV/ab2+zEuDfVwgsySPMpMlbO+4VfPUXvDIMsQLoBBBpoxqU3HMptYMZbKv5iyC6TV2+ XE27SvsNcVn5d4EMLK7pzdur21GQO7ZvSJd2NpruQsn5Dguxv91OXnoTbXh+01xJbPgH l1AlRE6GFwdhNKq9Cgc1ymjfhhF6BeK0RDn43nRAXWPZ087aL0zJHmkHj/Wv2f1nB+xs xtZA== MIME-Version: 1.0 X-Received: by 10.66.136.71 with SMTP id py7mr35297506pab.2.1380654969775; Tue, 01 Oct 2013 12:16:09 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.219.74 with HTTP; Tue, 1 Oct 2013 12:16:09 -0700 (PDT) In-Reply-To: <524AF1B5.4090907@freebsd.org> References: <201309291701.r8TH1gNv021817@svn.freebsd.org> <5248609D.7030105@freebsd.org> <5249F831.6050702@netfence.it> <524A8953.7080802@freebsd.org> <524AF1B5.4090907@freebsd.org> Date: Tue, 1 Oct 2013 12:16:09 -0700 X-Google-Sender-Auth: DKkjMs2k69nrDbEhmujInE9KLao Message-ID: Subject: Re: [HEADS UP] Fwd: svn commit: r328711 - in head: . Mk astro/viking cad/pdnmesh cad/repsnapper deskutils/pinot devel/xorg-macros emulators/catapult emulators/qemu-devel emulators/tme games/klavaro games/sea-defender ... From: Kevin Oberman To: Niclas Zeising Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-x11@freebsd.org" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2013 19:16:10 -0000 On Tue, Oct 1, 2013 at 9:00 AM, Niclas Zeising wrote: > On 10/01/13 17:01, Kevin Oberman wrote: > > On Tue, Oct 1, 2013 at 1:35 AM, Niclas Zeising > wrote: > > > >> On 10/01/13 00:16, Andrea Venturoli wrote: > >>> On 09/29/13 19:17, Niclas Zeising wrote: > >>>> HEADS UP! > >>>> > >>>> I just committed an update to the MESA graphics stack (libGL, dri) and > >>>> various other xorg ports. This mostly relates to people running with > >>>> WITH_NEW_XORG=, but be sure to check UPDATING before updating. > >>>> If you have any qeustions, don't hesitate to contact me or send a mail > >>>> to the freebsd-x11@FreeBSD.org mailing list. > >>>> Regards! > >>>> > >>> > >>> Great work! > >>> > >>> However, I think a little more info would be welcome by a lot of > people. > >>> > >>> E.g. > >>> In my case I have a Radeon card on 9.1... so: > >>> _ I don't have KMS, right? > >> > >> No, you don't. You have to update to the latest 10-CURRENT for that. > >> > >>> _ up to now WITH_NEW_XORG has prevented 3D hardware acceleration from > >>> working; is it still so with this update? > >> > >> I think so. Your best bet is to update to CURRENT. 10.0 isn't that far > >> off, and we are in a code freeze, so 10 is reasonably stable. > >> > >>> _ any caveat? > >> > >> None known, just read UPDATING. > >> Regards! > >> > > > > Not to be contrary, but I think this is an exceptionally bad time to > switch > > to current if you want stability. Maybe in another week, but not quite > yet. > > When code freeze is upon us, there are LOTS of commits of WIP, and things > > tend to break rather badly for a few days. These issues are normally > fixed > > fairly quickly, but it takes a little time and, from the issues raised in > > mail to current@, things are still a bit rough. > > > > I really don't want to discourage the use of 10.0 as more use is far > better > > for a solid release, but running current can be a bit more risky, and > > running it right after freeze is especially so. (So is running it right > > after current is re-opened after release.) I'd recommend waiting until > > around 10/10. (I like this date as it is the same whether your locality > > puts month or day first). By then current should be pretty stable. > > > > Just for the record, I've never really had any major trouble with > CURRENT, and run it regularly on my desktop and laptop. > Regards! > -- > Niclas Zeising > I ran it through the "entertaining" times of going from v4 to v6 and seldom had serious issues, but that was largely because I kept a close watch on the current@ mailer and was familiar with the process. I don't think either of us qualify as "typical" users. Nobody running head routinely really is and I think it can impact our perceptions. I can say with pretty high confidence that beginning of freeze and opening to major changes after a release are the least stable times for both STABLE and CURRENT. Instability with the freeze does not often last long. V5 was a notable exception. The thaw is often a bit more disruptive. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com