| *** diablo_rojo_phone is now known as Guest176 | 00:26 | |
| *** Guest176 is now known as diablo_rojo_phone | 00:27 | |
| *** blarnath is now known as d34dh0r53 | 06:53 | |
| *** blarnath is now known as d34dh0r53 | 07:01 | |
| *** blarnath is now known as d34dh0r53 | 07:24 | |
| *** ttx is now known as ttx_ | 11:14 | |
| *** pojadhav- is now known as pojadhav|ruck | 13:58 | |
| noonedeadpunk | Hey! I won't be able to catch today's meeting, as in area with really poor internet connection for the video call | 14:30 |
|---|---|---|
| jungleboyj | Won't be able to join for video call. Have conflicting meetings. | 15:26 |
| fungi | i can't video today, but will be available to answer questions on irc if people have need of me | 15:29 |
| dansmith | I know a bunch of other people are still out -- do we have enough for a quorum? | 15:30 |
| slaweq | dansmith I will be there | 15:32 |
| JayF | I'll be here but am extremely OK if we want to change venue to IRC | 15:42 |
| gmann | let's continue on video call as published in agenda too. we will see if we get quorum or not | 15:49 |
| gmann | tc-members: meeting time on zoom | 16:00 |
| gmann | link to join https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09#success | 16:00 |
| gmann | #startmeeting tc | 16:00 |
| opendevmeet | Meeting started Wed Jan 4 16:00:51 2023 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| opendevmeet | The meeting name has been set to 'tc' | 16:00 |
| gmann | link to join #link https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09#success | 16:01 |
| dansmith | rosmaita: around? | 16:02 |
| rosmaita | yeah, sorry, omw | 16:02 |
| knikolla[m] | I won’t be able to join this meeting | 16:03 |
| gmann | ack | 16:03 |
| fungi | don't forget, this week is the deadline to decide which projects will be capable of participating in the 2023.1/antelope release | 16:04 |
| gmann | link to agenda #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 16:04 |
| gmann | #topic Roll call | 16:04 |
| gmann | o/ | 16:04 |
| dansmith | o/ | 16:05 |
| rosmaita | o/ | 16:05 |
| slaweq | o/ | 16:05 |
| gmann | #topic Follow up on past action items | 16:05 |
| gmann | #link https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-21-16.00.html | 16:05 |
| gmann | #topic Gate health check | 16:05 |
| gmann | discussing tox4 things for stable branches | 16:12 |
| fungi | in case someone mentions the idea of "pinning" to an old version of tox, 1. there's no way to control the version of tox used by developers on their local systems, but also 2. if you set minversion in tox.ini (which most of our projects do) tox will automatically upgrade itself even if you installed an older version and even if that older version is technically new enough to satisfy the | 16:15 |
| fungi | minversion listed | 16:15 |
| fungi | however, it won't upgrade itself to version which doesn't support the python interpreter which called it, hence why some very old branches running tests on ubuntu-bionic are unaffected | 16:17 |
| gmann | seeing how much work stable branch and not all backport work as it is for stable branch, we can pin it for stable and project are ok to backport the fix if it work for them | 16:22 |
| gmann | #agree to pin tox<4 for stable branch and run latest tox for master | 16:22 |
| fungi | has someone successfully pinned tox on a stable branch? | 16:22 |
| fungi | from what i've seen, you'll have to remove the minversion from every tox.ini | 16:23 |
| gmann | fungi: you mean if minversion is 4.0.0 or current min also? | 16:23 |
| fungi | if it's set to anything at all, tox will automatically upgrade to the latest available version of tox from pypi on invocation | 16:23 |
| fungi | i recommend conferring with the people who have been working to address tox v4 issues before the tc members make decisions based on unfounded assumptions | 16:24 |
| gmann | while i tested it did not happen but may be need to check more testing | 16:25 |
| gmann | anyways, let test more after meeting and see if pinning on common job template work or not | 16:25 |
| gmann | #agree pin tox4 on stable if that really work that way but we need more testing | 16:26 |
| JayF | Lets just wait until next week, after some research, before putting some formal agreement on the record? | 16:27 |
| gmann | #undo | 16:27 |
| opendevmeet | Removing item from minutes: #agreed pin tox4 on stable if that really work that way but we need more testing | 16:27 |
| gmann | #undo | 16:27 |
| opendevmeet | Removing item from minutes: #agreed to pin tox<4 for stable branch and run latest tox for master | 16:27 |
| gmann | we will do more testing on this | 16:29 |
| gmann | #topic 2023.1 TC tracker checks: | 16:29 |
| gmann | #link https://etherpad.opendev.org/p/tc-2023.1-tracker | 16:29 |
| gmann | #topic Cleanup of PyPI maintainer list for OpenStack Projects | 16:30 |
| gmann | #link https://github.com/openstack/xstatic-font-awesome/pull/2 | 16:30 |
| gmann | #link https://pypi.org/project/murano/ | 16:31 |
| gmann | proposal is to push a resolution to keep only openstackci as maintainer in PyPi for openstack owned repo | 16:33 |
| fungi | for xstatic-font-awesome specifically, we should either give it back to the moinmoin community or fork it and publish under different names | 16:36 |
| fungi | since their needs apparently differ from ours | 16:37 |
| gmann | yeah | 16:37 |
| gmann | #topic Mistral situation | 16:44 |
| gmann | #action gmann to ping elod to check the mistral release status | 16:47 |
| gmann | #topic Recurring tasks check | 16:47 |
| gmann | Bare 'recheck' state | 16:47 |
| gmann | #link https://etherpad.opendev.org/p/recheck-weekly-summary | 16:47 |
| gmann | #topic Open Reviews | 16:49 |
| gmann | #link https://review.opendev.org/q/projects:openstack/governance+is:open | 16:49 |
| gmann | #endmeeting | 16:56 |
| opendevmeet | Meeting ended Wed Jan 4 16:56:48 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:56 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-04-16.00.html | 16:56 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-04-16.00.txt | 16:56 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-04-16.00.log.html | 16:56 |
| fungi | just to follow up on earlier discussion, the case we observed of tox upgrading itself was if the project sets tox.requires (e.g. in order to specify additional tox plugins) then tox will upgrade itself to the latest version available on pypi regardless of whether tox.min_version is already satisfied by the current version or even set at all | 18:17 |
| fungi | that can be solved by adding tox<4 to the requires list in tox.ini if it's being set, but does still require merging a change to the tox.ini on those branches | 18:23 |
| gmann | you mean for case where it is set for "requires virtualenv < 20.0" or only tox plugin | 18:24 |
| gmann | I am testing pinning on nova, cinder stable branches https://review.opendev.org/q/I0ca55abf9975c5a3f9713ac5dd5be39083e04554 https://review.opendev.org/q/I300e7804a27d08ecd239d1a7faaf2aaf3e07b9ee | 18:24 |
| dansmith | do any projects set tox.requires? nova has minver, but that doesn't seem to be a problem | 18:25 |
| fungi | if you set tox.requires at all, tox creates a new venv and installs itself and the listed requirements into that, then re-executes tox from that venv | 18:25 |
| fungi | and doesn't try to install the same version of tox which was originally invoked, just whatever's newest unless tox itself is also listed in the tox.requires in which case that gets passed in the pip command it runs | 18:26 |
| gmann | cinder has "requires = virtualenv>=20.4.2" let's see how it behave. I think that might be the reason rosmaita was seeing on cinder stable branch? but that was without pining | 18:27 |
| fungi | yeah, he's discussing that exact case with us in #opendev right now | 18:28 |
| gmann | tox<4 in tox.ini can be ok if project want to safe guard more when new tox break them or common job/template unpin or so | 18:28 |
| rosmaita | gmann: fungi: i will be offline for a bit (plumber just showed up) | 18:28 |
| rosmaita | this is the current stable/zed cinder patch without adding tox in the 'requires' in tox.ini (just uses the ensure_tox_version var in .zuul.yaml): https://review.opendev.org/c/openstack/cinder/+/868429 | 18:29 |
| rosmaita | don't know if that is helpful to look at or not | 18:29 |
| gmann | if that work then setting in common template should work too - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/867849 | 18:32 |
| fungi | oh, so it may be that tox.requires only comes into play when the listed requirements aren't already satisfied, since i don't see tox reinstalling itself in those jobs | 18:32 |
| dansmith | same with minver | 18:33 |
| fungi | codesearch suggests that the vast majority of tox.requires settings in our projects are for pinning some combination of pip, setuptools and virtualenv. an exception is https://opendev.org/openstack/tripleo-repos/src/branch/master/tox.ini#L5-L6 but that repo doesn't maintain stable branches | 18:37 |
| gmann | yeah and https://opendev.org/openstack/ansible-role-collect-logs/src/branch/master/tox.ini#L7 | 18:37 |
| gmann | but same case it is only master only repo | 18:37 |
| fungi | anyway, i expect pinning tox<4 is going to need tox.ini changes in stable branches of at least some projects in addition to whatever job configuration approach might be taken | 18:40 |
| dansmith | I think that's likely to be true of whatever solution we come up with | 18:42 |
| fungi | yep, just don't want to go thinking we can centrally pin tox in some branch-specific variants in openstack-zuul-jobs and call it a day | 18:46 |
| gmann | yeah and we will see if any specific case we hit in any projects | 18:53 |
| *** blarnath is now known as d34dh0r53 | 19:22 | |
| frickler | tc-members: since iiuc you have effectively taken over maintainance of openstack-manuals, how about having gerritbot announce patches here? also please check https://review.opendev.org/c/openstack/openstack-manuals/+/869245 and the tox4 fix below when you have time | 19:25 |
| gmann | frickler: thanks. +2. | 19:30 |
| dansmith | should I +W that or does it need more consensus? | 19:43 |
| gmann | you can +W | 19:44 |
| dansmith | it hath been done | 19:44 |
| gmann | normal code review with two +2 is applicable there | 19:45 |
| dansmith | cool, just checkin' | 19:45 |
| rosmaita | ok, i just +W'd the parent patch | 19:45 |
| gmann | cool | 19:45 |
| gmann | today meeting recording is available @ https://www.youtube.com/watch?v=4vR7iStJZe0 | 21:46 |
| *** dasm is now known as dasm|off | 22:14 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!