pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@lists.postgresql.org, Noah Misch <noah@leadboat.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Anastasia Lubennikova <lubennikovaav@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Melanie Plageman <melanieplageman@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: samay sharma <smilingsamay@gmail.com>
Subject: Re: CI and test improvements
Date: Wed, 01 Feb 2023 20:12:12 -0500
Message-ID: <1441145.1675300332@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+hUKG+kFpXfCsJQPJApkk7WrBFYYSao0V8q+cj88KQBV8XYRQ@mail.gmail.com>
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>
	<CA+hUKGL=z6-kU80nPTjWqV=Xo=mpM36Lca=ngTr4LqcCf=tHzQ@mail.gmail.com>
	<CA+hUKG+kFpXfCsJQPJApkk7WrBFYYSao0V8q+cj88KQBV8XYRQ@mail.gmail.com>

Thomas Munro <thomas.munro@gmail.com> 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





view thread (76+ messages)  latest in thread

Message-ID: <1441145.1675300332@sss.pgh.pa.us>
Permalink:  ../1441145.1675300332@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1441145.1675300332@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, thomas.munro@gmail.com, pryzby@telsasoft.com, andres@anarazel.de, andrew@dunslane.net, noah@leadboat.com, michael@paquier.xyz, lubennikovaav@gmail.com, robertmhaas@gmail.com, melanieplageman@gmail.com, peter.eisentraut@enterprisedb.com, daniel@yesql.se, smilingsamay@gmail.com
  Subject: Re: CI and test improvements
  In-Reply-To: <1441145.1675300332@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox