| *** bauzas08 is now known as bauzas0 | 09:34 | |
| frickler | retired or deprecated project's stable branches should not go eom, I agree. eol seems more suited, though I'm not sure we touch stable branches for retired projects at all usually, need to check on that | 10:00 |
|---|---|---|
| frickler | also x/networking-mlnx seems to still be using the official release roles/jobs, which IMO they shouldn't | 10:01 |
| frickler | all of these seem wrong to me, I don't think we can somehow block this on the zuul side, though, can we? https://opendev.org/x/networking-mlnx/src/branch/master/.zuul.yaml | 10:04 |
| frickler | like this surely makes it look like it was part of openstack https://docs.openstack.org/releasenotes/networking-mlnx/ | 10:10 |
| frickler | priteau: ^^ fyi it seems like you were the last person updating the zuul config. I assume this is just oversight, not intentional. I also agree that it is likely quite a bit of work do duplicate those parts of the templates that you actually do need for your testing | 10:12 |
| frickler | but I think it needs to be done | 10:12 |
| frickler | some jobs do work as intended, like the tarballs publishing ending up in https://tarballs.opendev.org/x/networking-mlnx/, but I'm not sure whether that is intentional and can be relied upon, or whether that is just pure chance | 10:14 |
| priteau | frickler: I didn't realise x/ projects shouldn't use the openstack templates. I see how the release notes could be a problem. FWIW, we have set up an external RTD site for the docs: https://networking-mlnx.readthedocs.io/en/latest/ | 13:46 |
| priteau | We could look at setting up one for the release notes as well. | 13:47 |
| priteau | Also, I think the goal is to try and make it official again | 13:47 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!