On Wed, Nov 13, 2019 at 02:32:37PM -0800, Kevin Fenzi wrote: > Greetings everyone. > > On 2019-11-26 fedora 29 will go end of life and no longer supported. > > We still have a number of things that are f29 (or older for various > reasons). I'd like everyone to look this over and see if you can't move > things to f31 (or at least f30) before the f29 eol. [...] > the-new-hotness: can we move to f31? There is some upcoming work on the-new-hotness, we should look at doing the upgrade at the same time > mdadpi: f27, but it moved to openshift, can we clean up the non > openshift instances and files please? +1 to nuke this one > notifs-backend: f27. I don't know what to do here. We need a > replacement, which we don't have. I'm afraid that upgrading will blow it > up, but I guess we could try and rollback? I may be able to port it to F30 but F31 will likely blow up because of py3 :( > ci-cc-rdu01: f28. Can we retire soon? Let's give this one until the end of the month and then nuke it :) > simple-koji-ci: f29. Can we upgrade to 31? or move it to communishift? Moving this one to communishift sounds like a good idea Pierre
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
