From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id ED/dGbetnWQTWgEASxT56A (envelope-from ) for ; Thu, 29 Jun 2023 18:13:43 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id iJHMGbetnWRWEQEA9RJhRA (envelope-from ) for ; Thu, 29 Jun 2023 18:13:43 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 1F8C751B4 for ; Thu, 29 Jun 2023 18:13:43 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qEuGX-0007Xf-5R; Thu, 29 Jun 2023 12:13:05 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qEuGU-0007WQ-Lu for guix-devel@gnu.org; Thu, 29 Jun 2023 12:13:02 -0400 Received: from mail-4316.protonmail.ch ([185.70.43.16]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qEuGS-0005VJ-6T for guix-devel@gnu.org; Thu, 29 Jun 2023 12:13:02 -0400 Date: Thu, 29 Jun 2023 16:12:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1688055177; x=1688314377; bh=gpmNULXqmwn3IzDLRgr8z8ZRHujJ+ervKCPxPczEj5c=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=WLQRJ0Ruz6piJYChWoW/tH2WMUPPa3Wy4Z4N/uMQ/bC3QCz2BvosCEkuYTHyn87gI cH0q9Vx3TXtUui4ZVTj8sxMVmwqKurqSkXTLY8YmYh+/PxzP6wOIfAbTsDzuKMT0Lo tMQJK+VIqeH0Vzn2o9/ocmGg+quzM8C92l9NglocQzxdkxIV3SJDAlp4FuT7IE3iGE yV8h2ypPF2EVKtz6M3J5fZmLDArp4vAsoYEB+yxVGNbna3DOmPNl5fF7Mjtl/V0wdB cx0kzrSplfGFKzs8BZtJQ59VhAilIJ5WhG35HGlB45D0cNK7A/p9ro73k9jDJclRAF 2KY6qGpwHoK+g== To: guix-devel From: John Kehayias Subject: Re: Branch (and team?) for mesa updates Message-ID: <87sfaa6yde.fsf@protonmail.com> Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.70.43.16; envelope-from=john.kehayias@protonmail.com; helo=mail-4316.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1688055223; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=gpmNULXqmwn3IzDLRgr8z8ZRHujJ+ervKCPxPczEj5c=; b=JFHjZ2gmjvL2l8RT+pubLxlkrKUM01qxmRmq/DiPHjC5RNfCF0UiiY7WbcQWL2tmmeUmj9 d3djNJko7FEap+JRh2ZeTLlIL6du6bLzzPNpGKkpSmqlnA6ZiMwvwJAmSCFiEvA9/dXo1E /3uu5fT4+9wLA8p+80bw8QuZ2d4VS3Ujn2dSe0J5cDthEV39PhQJO1eCB6x5F4uGqdFQ08 HsMlrsBv1G8XdEFLGQvz0nQJTn53r8Wvk1irnX7Cb0HyN5N2RQUQUNUYvwLkrWONiQkY/H 8DajRz5SBJFWZLu58KcoEzWDaRBZtdsss3dzf2OLMvmS4HnaJA+2wSxG99ITLw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=WLQRJ0Ru; dmarc=pass (policy=quarantine) header.from=protonmail.com; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1688055223; a=rsa-sha256; cv=none; b=Ov1W3CF3JfXt2wTgSZ5QZwHklhXJgu3dYZLG5koa8rI8gzuHW8qa58/UMJzwGLSdbtyIFb ftKkOfQaE6lCClTtFarJM4Ur6ayJ86Cj/VmHb7wNY5NCUPQ8YPY+4+sWorHBsiYnF7rMKT E5Wul7qOahhH0+LchD4tQXi5gmLp1uGhV5By+VkYwIyFpOVb4Gk1ZwfKkcuXuwasO4rmiQ wUaYWpa9Uq0Asn+MirnzYbMnGBOLvde65Qd+KX7B8cUdmoHf3TMj4nqbKDrNSv3IKVsirB EQciuXb8ZYao1YBaNvRMkoq0mxZzeiQy2wgsVnTExlV4wuSKfdnMxawB8z0yHg== X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -5.46 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=WLQRJ0Ru; dmarc=pass (policy=quarantine) header.from=protonmail.com; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 1F8C751B4 X-Spam-Score: -5.46 X-TUID: syZIgMaxA8d/ Hello again, On Mon, Jun 19, 2023 at 02:10 PM, John Kehayias wrote: > Hi everyone, > > With our move to a branching strategy for patches that require many > rebuilds, I would like to propose a branch for Mesa updates. Based on > how Mesa has been developed the last few years, there should be > frequent (roughly a couple of months or quicker) releases that > shouldn't be breaking anything or requiring lots of packaging work. > > Famous last words, I know, but at least in the last few years the only > big change I know of was the one we hit on the last core-updates cycle > with old hardware being dropped. The previous cycle had some build > changes, perhaps due to missing many intermediate version changes. > Both were rather self-contained and resolved quickly. > > So, I have submitted a patch for the latest stable release at > I'm aware of one other patch that > should also go here, are there any > others? > I've created a "mesa-updates" branch with these two commits (the one updating mesa has been updated to the latest version from last week). > I've tentatively labeled with "mesa-updates" as a proposed branch > name. With Mesa's release cycle I propose keeping this as a branch for > Mesa updates, and I suppose related required changes (say libdrm). If > everything goes smoothly, we can give the build farm some time to > build everything, check for any breakages, and then push to master > with substitutes available. Master can be merged into this branch just > prior to a patches going to this branch with the expectation merging > back to master will be soon after and changes are only affecting > packages that won't be touched on master anyway. I think this should > be relatively clean and straightforward, a good use of our new > branching/building strategy. > > Thoughts? Can someone set up a build job for this branch and/or let me > know how to do that? (I would also require access to Cuirass.) > I'll open a branch merge request issue later today as per new procedure for QA. Though I believe that only builds 2 branches, which is occupied at the moment. Or can someone set a separate build job specifically for mesa-updates, especially if we think it is a good idea to have this going forward? > Do we want a "Mesa team" or something a bit larger? Not sure what > exactly, since "graphics" is perhaps too broad. Happy to help > spearhead the Mesa front for Guix (the very package that got me first > involved in the patching process). > This is still a good question I think, of how we want to have a team(s) to handle things like xorg, wayland, mesa, and related packages. They are a bit all over the place in terms of scope and what they touch. For now I'd like to go ahead with a regular mesa-updates branch since that sees regular releases and is pretty self-contained currently. Thanks! John