On Thu, 2021-05-20 at 08:46 -0700, Kevin Fenzi wrote:
> On Thu, May 20, 2021 at 10:15:18AM -0400, Ben Cotton wrote:
> > On Wed, May 19, 2021 at 6:39 PM Adam Williamson
> > <adamw...@fedoraproject.org> wrote:
> > > 
> > > the drawback of that is we have to remember to manually update that
> > > list of versions each time a release branches. Which will inevitably
> > > get forgotten sometime. That's why I wanted to use the wildcards. But
> > > it's the best option I can think of for now. Sorry again for the
> > > trouble.
> > 
> > Would it be helpful for me to add this to the QA and/or RelEng
> > schedules for F35+? That way there's at least a written record that it
> > needs to be done, so if we forget we can't blame Past Us. :-)
> 
> Please do. :) 

Yeah, it would probably make sense for releng as it should happen at
exactly the point a release branches. Call it "Update Greenwave policy
product_versions" or something. There are several other policies in
that file that need updating at the same time as well as the openQA
one.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net


_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to