Open Stack

On Wed, 2022-07-20 at 11:49 +0000, Jeremy Stanley wrote:
> On 2022-07-20 09:34:18 +0100 (+0100), Sean Mooney wrote:
> [...]
> > for the A release the testing runtimes have not been chossen yet
> > but my expecation is we will drop 20.04 form the testing
> > requirements for master and move to 22.04 making 3.10 our default
> > python for tempest integration testing.
> 
> Unless I've misunderstood the recent TC discussions around supported
> platform overlap, the new release cadence, and upgrade testing, it's
> my understanding that we'll still at least need to test that we can
> upgrade from Zed to Anchovy/Anteater/Antelope on Ubuntu 20.04 LTS
ah correct this is not really related to the new lifecycle.
we will need to test with ubuntu 20.04 for grenade or other upgrade jobs
since we do not update the os in those jobs so deploy on the older release.
> (future A->B and A->C upgrade testing will be able to just use 22.04
> LTS though), so it's not going away entirely for master branch tests
> until B.
yes 22.04 can only become the base of the grenade job for A->B
all the standard jobs should mvoe to 22.04 in B ideally which means
we need to keep 3.8 until B since that is the default in 20.04
in B we can increase the minium to 3.9 and add 3.11 based on the timeline
you explain below since that would better align with our developemnt cycle.
> 
> > assuming the python 3.11 interperter and ideally standard libary
> > are aviabel as a package to install on 22.04 we should be able to
> > add a non vovting py3.11 tox job to replace our current py3.10 job
> > and perhaps even have a periodic-weekly python 3.11 tempest job.
> [...]
> 
> In the past, Ubuntu has waited to backport a new Python minor
> version until after its .1 point release is available. For 3.11.1
> that's scheduled to be approximately 2 months after 3.11.0 is done,
> so expect early December. That puts any Jammy backport of it into
> 2023 at the earliest, I expect, at best a couple of months before we
> release so probably not soon enough in the cycle for meaningful
> testing before master is open for B cycle work.
ack so ya that likely means it cant be considerd a required target for A
but could be optioanlly tested by some projects once its avaiable.
is assume there is no reason not to add 3.10 to the requried testing runtimes
for A based on ubuntu 22.04 form its current best effort status.