Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pNO9F-0001Ij-Nv for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Feb 2023 01:12:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pNO9E-0001bW-L4 for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Feb 2023 01:12:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pNO9E-0001bJ-BI for pgsql-hackers@lists.postgresql.org; Thu, 02 Feb 2023 01:12:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pNO9C-0000p4-5Y for pgsql-hackers@lists.postgresql.org; Thu, 02 Feb 2023 01:12:19 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 3121CCh21441146; Wed, 1 Feb 2023 20:12:12 -0500 From: Tom Lane To: Thomas Munro cc: Justin Pryzby , Andres Freund , Andrew Dunstan , pgsql-hackers@lists.postgresql.org, Noah Misch , Michael Paquier , Anastasia Lubennikova , Robert Haas , Melanie Plageman , Peter Eisentraut , Daniel Gustafsson , samay sharma Subject: Re: CI and test improvements In-reply-to: References: <20220528153741.GK19626@telsasoft.com> <20220828144447.GA21897@telsasoft.com> <20220828160752.l5l66k3eptokzhzj@awork3.anarazel.de> <20220828171029.GO2342@telsasoft.com> <20220828212802.r6eymfffrgr3lxxt@awork3.anarazel.de> <20220910200542.GX31833@telsasoft.com> <20221104235412.GE16921@telsasoft.com> <20221105015946.yrxijqb7h4rqhp6d@awork3.anarazel.de> <20221113235303.GA26337@telsasoft.com> <20221121224542.p2zapvyvb7objluw@alap3.anarazel.de> <20221122225744.GF11463@telsasoft.com> Comments: In-reply-to Thomas Munro message dated "Thu, 02 Feb 2023 14:02:25 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1441144.1675300332.1@sss.pgh.pa.us> Date: Wed, 01 Feb 2023 20:12:12 -0500 Message-ID: <1441145.1675300332@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > Some observations: > * macOS has a new release every year in June[1] > * updates cease after three years[1] > * thus three releases are in support (by that definition) at a time > * we need an image on Cirrus; 13 appeared ~1 month later[2] > * we need Homebrew support; 13 appeared ~3 months later[3] > * we have 13 and 12 in the buildfarm, but no 11 > * it's common for developers but uncommon for servers/deployment > So what should our policy be on when to roll the CI image forward? I > guess around New Year/now (~6 months after release) is a good time and > we should just do it. Anyone got a reason why we should wait? Our > other CI OSes have slower major version release cycles and longer > lives, so it's not quite the same hamster wheel of upgrades. I'd argue that developers are probably the kind of people who update their OS sooner rather than later --- I've usually updated my laptop and at least one BF animal to $latest macOS within a month or so of the dot-zero release. So waiting 6 months seems to me like CI will be behind the users, which will be unhelpful. I'd rather drop the oldest release sooner, if we need to hold down the number of macOS revisions under test. regards, tom lane