From owner-svn-ports-head@freebsd.org Fri Jul 6 17:35:44 2018 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C1DB103E5D0; Fri, 6 Jul 2018 17:35:44 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 116A98D064; Fri, 6 Jul 2018 17:35:44 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 03F5B9952; Fri, 6 Jul 2018 17:35:43 +0000 (UTC) From: Jan Beich To: Niclas Zeising Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r474016 - in head/graphics/mesa-dri: . files References: <201807061606.w66G6ZOa066494@repo.freebsd.org> <36ww-i99x-wny@FreeBSD.org> Date: Fri, 06 Jul 2018 19:35:40 +0200 In-Reply-To: (Niclas Zeising's message of "Fri, 6 Jul 2018 19:11:07 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2018 17:35:44 -0000 Niclas Zeising writes: > On 07/06/18 19:06, Jan Beich wrote: > >> Niclas Zeising writes: >> >>> Author: zeising >>> Date: Fri Jul 6 16:06:35 2018 >>> New Revision: 474016 >>> URL: https://svnweb.freebsd.org/changeset/ports/474016 >>> >>> Log: >>> graphics/mesa: update to 18.1.3 >> >> Please, request MFH to 2018Q3 throughout 18.1.* life. After /head >> updates to 18.2.0 (or later) request direct commit(s) instead. >> Make sure to ping ports-secteam@ for each week they don't respond. ;) > > Why? This is not a security update. Reliability (e.g., regression fixes). Semantic versioning in Mesa appears to be more about drivers rather than ABI of libraries. 18.2.0 is likely to degrade stability but CFTs are often too opaque to notice minor issues (e.g., only some apps regressing).