On Wed, 2021-01-20 at 17:11 +0100, Kamil Paral wrote:
On Tue, Jan 19, 2021 at 6:44 PM Mark Pearson
<markpearson(a)lenovo.com> wrote:
> Release cadence is once. We just can't update our preload images that
> often - there's a long test cycle, and energy certification that goes
> with that image. It's one of the reasons the X1C8 is still shipping with
> Fedora32, and P1G3 and P15 (soon!) will be with F33 for a long time. The
> only reason to update would be a critical bug that couldn't be fixed
> with an update once the platform was received.
>
If the cadence is once in a long time (related to new hardware
introductions, so possibly once a year or similar), I think the best
approach here is to have releng manually trigger an F33 Workstation Live
image compose using the current updates repo. Assuming it's not a problem
for them. We (the QA) can then trigger an OpenQA test run on it, create the
release validation test matrices for it, and even ask the community in
large to perform some manual tests if they have time. I believe some of us
would devote some time to make sure at least the basics work correctly. I'm
not sure if all the plumbing for this one-off compose is ready (in fedfind,
relval, openqa and wherever else needed), but Adam will know more.
Yeah, I don't think that should be really tricky for anyone. I'd
suggest we just run it as a post-release nightly compose rather than a
candidate and don't give it any kind of label. I don't think it should
be hard for releng to run that, and I should be able to run openQA
tests and even create a validation event if necessary, I might need to
metaphorically whang a few things with a hammer because it won't quite
fit the normal flows but it shouldn't be a big deal.
Also, I forgot to mention it'll obviously be completely impossible for
this to work without Lenovo shipping me some hardware for,
uh...testing. Yup. That's definitely non-negotiable. Two of everything.
:D
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net