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 1lC3H1-0005fb-KT for buildfarm-members@arkaria.postgresql.org; Tue, 16 Feb 2021 16:32:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lC3H0-0004Ax-J8 for buildfarm-members@arkaria.postgresql.org; Tue, 16 Feb 2021 16:32:26 +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 1lC3H0-0004Ai-EI for buildfarm-members@lists.postgresql.org; Tue, 16 Feb 2021 16:32:26 +0000 Received: from relay8-d.mail.gandi.net ([217.70.183.201]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lC3Gx-0001ys-Kk for buildfarm-members@lists.postgresql.org; Tue, 16 Feb 2021 16:32:25 +0000 X-Originating-IP: 99.10.92.30 Received: from [192.168.10.146] (99-10-92-30.lightspeed.rlghnc.sbcglobal.net [99.10.92.30]) (Authenticated sender: adsend@dunslane.net) by relay8-d.mail.gandi.net (Postfix) with ESMTPSA id 146A51BF20B; Tue, 16 Feb 2021 16:32:18 +0000 (UTC) Subject: Re: Postgres 9.5 branch is now EOL To: Tom Lane , buildfarm-members@lists.postgresql.org References: <1477846.1613069015@sss.pgh.pa.us> From: Andrew Dunstan Message-ID: Date: Tue, 16 Feb 2021 11:32:16 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: <1477846.1613069015@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/11/21 1:43 PM, Tom Lane wrote: > This week's 9.5.25 release is the end of the support lifetime > for the REL9_5_STABLE branch. It looks like pretty much all > active buildfarm animals have reported in on the final commit > there, so it's time to shut down buildfarm support for that > branch. If you have manual configuration determining which > branches get built, please update it. If you use run_branches.pl, > you shouldn't have to do anything --- whenever Andrew updates > the active-branches list on the buildfarm server, that will > take effect automatically. I've done this now. > > (Though you might want to clean out the per-branch directory > in your buildfarm work area, just to reclaim some disk space. > AFAIK that's not automatic.) > > No, it's not automatic. Note that if you use git_use_workdirs and rm_worktrees they take up virtually no space. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com