| *** ykarel is now known as ykarel|away | 12:23 | |
| *** pojadhav is now known as pojadhav|afk | 13:53 | |
| spotz_ | Hey belmoreira | 14:58 |
|---|---|---|
| belmoreira | hi | 14:58 |
| gmann | tc-members: meeting time | 15:00 |
| gmann | #startmeeting tc | 15:00 |
| opendevmeet | Meeting started Thu Feb 10 15:00:10 2022 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'tc' | 15:00 |
| gmann | #topic Roll call | 15:00 |
| dansmith | belmoreira: you around after the meeting to chat about release cycle? | 15:00 |
| gmann | o/ | 15:00 |
| dansmith | o/ | 15:00 |
| spotz_ | O/ | 15:00 |
| belmoreira | o/ | 15:00 |
| belmoreira | dansmith yes, I can stay longer | 15:00 |
| dansmith | cool | 15:00 |
| jungleboyj | o/ | 15:00 |
| yoctozepto | o/ | 15:01 |
| ricolin | o/ | 15:01 |
| dmendiza[m] | \o | 15:01 |
| diablo_rojo_phone | O/ | 15:01 |
| gmann | #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 15:02 |
| gmann | ^^ agenda for today meeting | 15:02 |
| gmann | absent members: Rico Lin (ricolin), Chinese New Year vacation | 15:02 |
| gmann | let's start | 15:02 |
| gmann | #topic Follow up on past action items | 15:03 |
| ricolin | that's a mistake:) | 15:03 |
| ricolin | I'm presented:) | 15:03 |
| gmann | ricolin: ohk, nice | 15:03 |
| gmann | sorry i missed to remove it from there may be | 15:03 |
| ricolin | NP | 15:03 |
| gmann | no action item to track from previous meeting #link https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-03-15.00.html | 15:04 |
| gmann | #topic Gate health check | 15:04 |
| gmann | what's news on gate this week | 15:04 |
| dansmith | I've seen some instability this week, I dunno about others | 15:04 |
| dansmith | I haven't collected any hard data, but I've seen a lot of 'recheck cinder' type things | 15:05 |
| dansmith | I'll try to pay more attention over the next week and see if I can report any patterns | 15:05 |
| gmann | ok | 15:05 |
| gmann | there is volume detach issue occurring 100% on centos9 stream job | 15:06 |
| gmann | #link https://bugs.launchpad.net/nova/+bug/1960346 | 15:06 |
| gmann | and neutron stable gate got broken due to tempest change which is also fixed now and green | 15:06 |
| gmann | and centos8-stream is still unstable and jobs are non voting. | 15:07 |
| gmann | *centos8-stream jobs | 15:07 |
| yoctozepto | well, without "jobs" it's probably still true ;-) | 15:08 |
| fungi | we also restored the centos-8 nodeset temporarily, pointing it at centos-8-stream labels, because the nodeset removal deadlocked cleanup in jobs which relied on it | 15:09 |
| yoctozepto | oh my | 15:09 |
| gmann | humm | 15:09 |
| fungi | though we're looking at a more obvious alternative so that jobs using the centos-8 nodeset will return node_failure results (therefore no risk that they succeed, but still won't block cleanup changes) | 15:10 |
| gmann | there are stable branch jobs using the nodeset and we could not remove it from devstack but I will give another try with fixes on stable branches | 15:10 |
| spotz_ | Fungi could those nodes be told to use stream repos? | 15:11 |
| yoctozepto | fungi: that sounds sensible | 15:11 |
| fungi | the basic problem is that if you have a job which relies on a nodeset, and that nodeset is no longer defined, you can't merge a change to remove the job or alter its nodeset | 15:11 |
| spotz_ | Ouch | 15:11 |
| yoctozepto | zuul's quirk | 15:11 |
| fungi | because zuul expects the initial state it's going to compare the change against to have resolveable configuration | 15:12 |
| gmann | yeah, do we have list of how many jobs using it. I know few of the cinder stable/victoria | 15:12 |
| fungi | i'm not sure if anyone has put anything together, no | 15:13 |
| fungi | i know jrosser was trying to work through a bunch of cleanup for it in openstack-ansible repos | 15:13 |
| gmann | k, I will work on devstack side to remvove the node and see how many we can cleanup on that | 15:13 |
| gmann | nova side I fixed but still need more to fix | 15:14 |
| gmann | anything else on gate? | 15:15 |
| gmann | #topic Z Release Cycle Name | 15:16 |
| gmann | ranked names are under trademark checks by foundation. may be we should be ready by next week | 15:16 |
| yoctozepto | hopefully Zen passes | 15:16 |
| jungleboyj | Any feeling for what the result will be? | 15:17 |
| gmann | Zombie :) | 15:17 |
| belmoreira | :) | 15:17 |
| dansmith | heh | 15:17 |
| * jungleboyj laughs | 15:17 | |
| spotz_ | It has grown on me | 15:17 |
| jungleboyj | Zen or Zombie? | 15:17 |
| spotz_ | Zombie | 15:18 |
| yoctozepto | lol | 15:18 |
| jungleboyj | :-) | 15:18 |
| jungleboyj | Quote of the day 'Zombie is growing on me.' | 15:18 |
| spotz_ | Hehe | 15:18 |
| yoctozepto | on spotz_* | 15:18 |
| yoctozepto | anyhow, I guess gmann please continue | 15:19 |
| gmann | :) | 15:19 |
| gmann | on the release name, belmoreira will you be able to put the new name process up for review what we discussed in last PTG ? or let us know if you need help. | 15:19 |
| belmoreira | sure. I think is consensual that we just restart the alphabet. Or someone as a different opinion? | 15:20 |
| yoctozepto | tbh, I wanted to switch to years | 15:21 |
| fungi | we'll also need to scramble to update the election repo during campaigning, to swap out the z placeholder for whatever name is selected | 15:21 |
| dansmith | as opposed to what? start with the klingon alphabet? | 15:21 |
| dansmith | oh years | 15:21 |
| yoctozepto | yeah | 15:21 |
| gmann | 20xx.1 & 20xx.2 ? | 15:21 |
| yoctozepto | or with months, like ubuntu | 15:22 |
| yoctozepto | both are fine | 15:22 |
| dansmith | well, if we go with a tick/tock release cycle, | 15:22 |
| dansmith | we could also get more creative with the .1 and .2 so they're meaningful | 15:22 |
| dansmith | but yeah, I'm not opposed to years at all | 15:23 |
| belmoreira | honestly I like the idea... but we lose the fun of naming the release | 15:23 |
| yoctozepto | 2022.duck 2022.yeah | 15:23 |
| dansmith | the names all kinda blend together now, and I do love knowing that my 12.04 machine is almost ten years old :D | 15:23 |
| belmoreira | or we keep the relase name as well, like ubuntu | 15:23 |
| dansmith | yeah | 15:23 |
| yoctozepto | belmoreira: yeah | 15:23 |
| gmann | I like that <year>.<name> ? | 15:24 |
| gmann | or like ubuntu | 15:24 |
| diablo_rojo_phone | Yeah that sounds good. | 15:24 |
| belmoreira | but in that case we don't need to be attached to the alphabet (following the letters...) | 15:24 |
| knikolla | I have to confess I had to google the alphabet to completely remember the order of those last few letters (hi all :) | 15:24 |
| gmann | but single name not double | 15:24 |
| gmann | knikolla: hi. | 15:24 |
| diablo_rojo_phone | knikolla: I often still have to sing the song to myself lol | 15:24 |
| belmoreira | gmann :) | 15:24 |
| jungleboyj | :-) | 15:25 |
| dansmith | gmann: or, make it harder: | 15:25 |
| yoctozepto | alphabet song ftw | 15:25 |
| dansmith | all names after this have to be a single word with the proper repeated letter | 15:25 |
| dansmith | aardvark for example | 15:25 |
| dansmith | B will be a challenge | 15:25 |
| spotz_ | I like names they’re fun | 15:25 |
| yoctozepto | lol | 15:25 |
| dansmith | Bubble, Bobble | 15:25 |
| dansmith | Capuccino | 15:25 |
| yoctozepto | yeah, names are fun | 15:25 |
| jungleboyj | I don't think we want to remove the name aspect. | 15:25 |
| jungleboyj | If we append the year that is fine with me. | 15:25 |
| belmoreira | jungleboyj +1 | 15:26 |
| dansmith | we technically have version numbers now, which I can never remember, | 15:26 |
| jungleboyj | Or pre-pend I should say. | 15:26 |
| gmann | ok, let's put it for review and then we can discuss more ideas too along with the one we discussed now | 15:26 |
| dansmith | so switching to years will likely involve some work by people I imagine | 15:26 |
| belmoreira | but do you think we need to follow the alphabet if we have the year? | 15:26 |
| yoctozepto | we can forget the alphabet song then | 15:26 |
| yoctozepto | let people propose names they feel are current | 15:27 |
| yoctozepto | like | 15:27 |
| jungleboyj | I personally like keeping the alphabet as it keeps the feeling of progression. | 15:27 |
| yoctozepto | OpenStack Covid Edition | 15:27 |
| yoctozepto | 2022.10 | 15:27 |
| spotz_ | Are we just going to confuse everyone! | 15:27 |
| knikolla | I feel names bring a sense of community with the voting process | 15:28 |
| jungleboyj | spotz_: I think that is a legitimate concern. | 15:28 |
| jungleboyj | knikolla: ++ | 15:28 |
| yoctozepto | I dunno, the year would be just fine for me | 15:28 |
| gmann | knikolla: +1 | 15:28 |
| dansmith | knikolla: except we don't do it anymore :) | 15:28 |
| dansmith | I mean, lately. | 15:28 |
| yoctozepto | yeah | 15:28 |
| gmann | I like year followed by elected name but yeah let's put those ideas we discussed today and then we can continue discussion in gerrit ? | 15:29 |
| yoctozepto | +1 | 15:29 |
| gmann | and if we go with the voting system then we will change that from TC to community members | 15:30 |
| belmoreira | +1 | 15:30 |
| gmann | belmoreira: is it fine to add action item for you? | 15:30 |
| jungleboyj | +1 | 15:30 |
| belmoreira | gmann sure | 15:30 |
| gmann | #action belmoreira to propose the next release naming ideas | 15:30 |
| gmann | belmoreira: thanks | 15:30 |
| gmann | #topic Z cycle Technical Elections | 15:31 |
| gmann | nomination for PTL and TC are open and until 15th Feb | 15:31 |
| gmann | #link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027117.html | 15:32 |
| gmann | till now we have only 5 PTL and 1 TC nomination | 15:32 |
| gmann | yoctozepto: belmoreira : announced that they are not running TC in next term. | 15:32 |
| gmann | thanks again both of you for your contribution. | 15:32 |
| gmann | but as you know until this election is over you are in TC term or you re-decide to serve next term too :) | 15:33 |
| spotz_ | Hehe | 15:33 |
| jungleboyj | You can't get away that quickly! | 15:33 |
| yoctozepto | TC4life | 15:33 |
| gmann | :) +1 | 15:33 |
| belmoreira | yeah, the farewell is in few weeks :) | 15:34 |
| gmann | and I hope ricolin and mnaser will run as their term is also completing this election. | 15:34 |
| gmann | but feel free to encourage members for PTL or TC which you know are interested or you think better to have in group | 15:35 |
| yoctozepto | I will be around on the mailing list after the farewell as well and you can always send me an email to my primary address :-) | 15:35 |
| ricolin | I might not have much time for TC works in the following months, but will see before the Nomination end | 15:36 |
| gmann | yoctozepto: +1, cool. | 15:36 |
| gmann | ricolin: thanks. | 15:36 |
| yoctozepto | what if there are no more nominations though? | 15:36 |
| yoctozepto | will you reduce the TC size again? | 15:36 |
| gmann | yeah, we will see what to do. either find someone or discuss on reducing the seat again | 15:37 |
| ricolin | +1 on encourage new TC to join | 15:37 |
| jungleboyj | +1 | 15:37 |
| gmann | yeah, I think we have lot of technical work to drive in coming cycles so having 9 members in group will be helpful but let's see | 15:38 |
| gmann | for more election updates, we will discuss in election channel and update highlights in this channel too | 15:39 |
| belmoreira | honestly I don't expect this to be a problem for the TC. Usually people only nominate themselves close to the end of the process | 15:39 |
| gmann | yeah, even for PTL also. at the end we see lot of nomination | 15:39 |
| spotz_ | I did it early so I wouldn’t forget to fit review again | 15:39 |
| yoctozepto | even after the end | 15:39 |
| jungleboyj | That was what I figured. | 15:39 |
| jungleboyj | spotz_: Good job! :-) | 15:40 |
| gmann | ricolin: just to know till when is the Chinese vacation ? | 15:40 |
| spotz_ | Hehe | 15:40 |
| jungleboyj | gmann: It officially ended on last Sunday. | 15:40 |
| gmann | spotz_: +1 | 15:40 |
| jungleboyj | Lots of people take the following week off. | 15:40 |
| ricolin | gmann, entire last week | 15:40 |
| jungleboyj | ++ | 15:41 |
| gmann | ok so we are good in term of nomination dates. I thought it conflict and many members might miss notification | 15:41 |
| ricolin | and give or take few days front or back | 15:41 |
| ricolin | yes | 15:41 |
| ricolin | definitely okay | 15:41 |
| gmann | ricolin: please spread the election nomination in local groups like wechat etc in case | 15:41 |
| ricolin | will do | 15:41 |
| gmann | in case they missed the ML | 15:41 |
| gmann | ricolin: thanks | 15:41 |
| gmann | #topic Dropping tags framework - next steps (yoctozepto) | 15:42 |
| yoctozepto | yup | 15:42 |
| yoctozepto | so, the releases repo needs to be adapted to stop relying on tags | 15:42 |
| gmann | part1 is up for review #link https://review.opendev.org/c/openstack/governance/+/822900 | 15:42 |
| gmann | yoctozepto: and openstack website too. | 15:43 |
| yoctozepto | ah, good catch, I forgot, thanks gmann | 15:43 |
| gmann | I am not sure I can help on this in this cycle but anyone to help on replacing it for release scripts etc? | 15:43 |
| gmann | or yoctozepto can you please check in release channel if release membrs can help here | 15:45 |
| yoctozepto | the other thing is new placement of the contentss | 15:45 |
| yoctozepto | I will start a thread on the ML | 15:45 |
| fungi | if there's a timeframe for this, i can move the vulnerability:managed tag guidelines into the openstack/ossa repo | 15:46 |
| yoctozepto | fungi: thanks, that makes sense | 15:46 |
| fungi | the vmt relies on that as a means of documenting expectations, but we don't really have any tooling relying on it directly | 15:46 |
| gmann | fungi: thanks | 15:46 |
| yoctozepto | and then how do we want to track which projects are vmt? | 15:47 |
| gmann | fungi: we have few document/process in project team guide too #link https://docs.openstack.org/project-team-guide/vulnerability-management.html | 15:47 |
| fungi | yoctozepto: the vmt can just maintain a list in the ossa repo | 15:47 |
| gmann | fungi: it is fine whatever way you want to arrange them in one place | 15:47 |
| gmann | +1 | 15:48 |
| yoctozepto | ack, perfect | 15:48 |
| fungi | gmann: thanks for bringing that up, i had forgotten it was in there | 15:48 |
| gmann | fungi: on timeline, no hard timeline but we planned to finish it before Yoga release(final release). | 15:48 |
| fungi | and yeah, whatever makes sense to be on the security.o.o site we'll put in the ossa repo and we can also move some stuff into the project team guide as appropriate | 15:49 |
| gmann | sounds good | 15:49 |
| yoctozepto | ok, so vmt is solved, only stable (releases) and deprecation policy remain | 15:50 |
| yoctozepto | presumably stable goes to releases team | 15:50 |
| gmann | yoctozepto: and for standard deprecation tag, we can move in project-team-guide under technical-guidelines (what we planned to make new dir) ? | 15:50 |
| yoctozepto | hmm, makes sense | 15:50 |
| gmann | yoctozepto: stable also we have in proeject-team-guide #link https://docs.openstack.org/project-team-guide/stable-branches.html | 15:51 |
| yoctozepto | and projects are free to follow that | 15:51 |
| yoctozepto | gmann: yeah, I mean tracking | 15:51 |
| gmann | ohk | 15:51 |
| yoctozepto | but maybe it's irrelevant | 15:51 |
| yoctozepto | I mean, it was only on the paper anyway | 15:52 |
| yoctozepto | (I hope that expression makes sense in English) | 15:52 |
| gmann | project/repo having stable branch are supposed to follow it so yeah we do not need to track as list I think | 15:52 |
| yoctozepto | ok, so similar to deprecation | 15:53 |
| gmann | supposed to follow as per new process | 15:53 |
| yoctozepto | any other opinions? | 15:53 |
| gmann | IMO, for deprecation also I think same. we will have guidelines and project will follow that as they are doing now. list is not necessary to maintain | 15:54 |
| yoctozepto | ok, /me like | 15:55 |
| gmann | yeah, any other opinion? especially from users point of view | 15:55 |
| opendevreview | Merged openstack/governance master: Add timelines to few of the Chair duties. https://review.opendev.org/c/openstack/governance/+/828062 | 15:56 |
| yoctozepto | tough crowd | 15:56 |
| yoctozepto | guess it means everyone agrees | 15:57 |
| yoctozepto | thanks gmann and fungi for discussion | 15:57 |
| gmann | hope so, please push the changes and we can get more feedback there if there is any | 15:57 |
| yoctozepto | +1 | 15:57 |
| gmann | 3 min left let's move next | 15:57 |
| gmann | thanks yoctozepto for working on it | 15:58 |
| gmann | #Open Reviews | 15:58 |
| gmann | 3 open review #link https://review.opendev.org/q/projects:openstack/governance+is:open | 15:58 |
| gmann | 1 is in gate to merge | 15:58 |
| gmann | please review those | 15:58 |
| gmann | one last thing | 15:58 |
| gmann | right after this meeting we will have release cadence discussion @ https://meetpad.opendev.org/OpenStackReleasecadence | 15:59 |
| gmann | please join there | 15:59 |
| gmann | that is all from my side today ? | 15:59 |
| * yoctozepto not around for it | 15:59 | |
| gmann | thanks everyone for joining. | 15:59 |
| yoctozepto | thanks gmann for chairing | 15:59 |
| gmann | #endmeeting | 15:59 |
| opendevmeet | Meeting ended Thu Feb 10 15:59:36 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:59 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-10-15.00.html | 15:59 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-10-15.00.txt | 15:59 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-10-15.00.log.html | 15:59 |
| * yoctozepto off | 15:59 | |
| jungleboyj | Thanks! | 15:59 |
| dansmith | gmann: can you paste the link for the release cycle discussion? | 16:00 |
| gmann | dansmith: https://meetpad.opendev.org/OpenStackReleasecadence | 16:00 |
| fungi | note that jitsi-meet room names are case-insensitive but etherpad pad names are case-sensitive, so it's preferable to use all lower-case meetpad room names or else the room name and the pad name won't match up | 16:01 |
| gmann | fungi: ack, thanks. did not know that | 16:02 |
| fungi | in short, the pad being shared in the OpenStackReleasecadence room is the openstackreleasecadence pad | 16:02 |
| fungi | we've (opendev) been looking into ways to switch etherpad to be case-insensitive as well, but currently have thousands of collisions between pad names we'd need to resolve first to put that into place | 16:03 |
| opendevreview | Merged openstack/governance master: Remove security-specs from security sig https://review.opendev.org/c/openstack/governance/+/828018 | 16:07 |
| *** tkajinam is now known as Guest210 | 16:30 | |
| dansmith | gmann: trying to get my head wrapped around some stable math here | 17:40 |
| dansmith | we support 18 months of old releases, which means that close to the end of a cycle before release, that's verging on 24 calendar months of oldness right? | 17:41 |
| gmann | dansmith: we usually release cycle and then make oldest release to extended maintenance so there is always window and more then 3 releases in support for some time. with new model, I think 24 months idea is also for same reason that to support at least two tick at the same time (if we are on time to move them to Extended maintenance or EOl on time ) | 17:47 |
| dansmith | gmann: okay, so hypothetically, | 17:49 |
| gmann | say A is first tick, after 12 month C is 2nd so A and C supported (along with B) and then with release of E, A, B goes away | 17:49 |
| dansmith | we release C, and Z is still supported until D? | 17:49 |
| dansmith | ah, good, | 17:49 |
| dansmith | that's what I wanted but was getting confused, | 17:49 |
| dansmith | so really two ticks are only supported during a tock, | 17:49 |
| dansmith | once we have another tick, we drop the oldest tick so only two ticks are supported at any given point | 17:50 |
| dansmith | ignore my second-to-last.. the easiest way is "only two ticks at any given point" | 17:50 |
| gmann | yeah, Z we need to see but after we start tick with A. -> A, B, C,D will be supported which need 24 month and with E release A,B goes away and C,D,E is in support..... | 17:50 |
| dansmith | that's kinda 12 months of support, but if we continue supporting the tock previous (B) then that would be 18 as today | 17:50 |
| gmann | yeah | 17:51 |
| dansmith | ack | 17:51 |
| gmann | or in simple term, oldest supported release will be always tick not tock. | 17:52 |
| dansmith | ack | 17:53 |
| dansmith | I will put examples in here :) | 17:53 |
| gmann | A (release in 2022) goes away only after E (release in 2024) is released so 24 month support :) | 17:55 |
| gmann | years as example, as they are not correct though | 17:56 |
| dansmith | I'm putting a table in here with an example sequence | 18:00 |
| gmann | k | 18:01 |
| dansmith | so you can review for correctness :D | 18:01 |
| dansmith | hmm, is this my doing? Warning, treated as error: | 18:12 |
| dansmith | Failed to read build info file: ValueError("build info file is broken: IndexError('list index out of range')") | 18:12 |
| fungi | is that from a sphinx build? | 18:14 |
| dansmith | yeah, in governance | 18:14 |
| fungi | make sure you clear out the build dir if tox isn't already configured to | 18:15 |
| fungi | you can also stash your changes and rerun on the head state of course, to rule out your diff being a problem | 18:15 |
| dansmith | that got me farther, but gives me this now: | 18:16 |
| dansmith | Exception occurred: | 18:16 |
| dansmith | File "/home/dan/governance/doc/source/_exts/atcs.py", line 73, in run | 18:16 |
| dansmith | raise ValueError('No project %r in projects.yaml' % (project,)) | 18:16 |
| dansmith | ValueError: No project 'astara-appliance' in projects.yaml | 18:16 |
| fungi | and that's after deleting all of doc/build ? | 18:17 |
| dansmith | yup | 18:17 |
| gmann | humm, let me run | 18:17 |
| dansmith | it doesn't even seem to be running resolutions/ before it fails, so I don't think it's related to my stuff | 18:17 |
| dansmith | yeah, confirmed | 18:18 |
| fungi | still seems like a crufty tree problem | 18:18 |
| fungi | i'm trying to reproduce it myself | 18:18 |
| fungi | but atcs.py shouldn't care about astara, it's been in legacy for a long time | 18:18 |
| dansmith | trying a fresh clone | 18:19 |
| gmann | it is successfully in my case, with sphinx 4.4.0 | 18:19 |
| dansmith | okay yeah, makes it past that on a fresh clone | 18:19 |
| dansmith | what else can I delete? | 18:19 |
| fungi | you could `git clean -dfx` | 18:19 |
| fungi | which should report what it removes | 18:19 |
| dansmith | removed a bunch of reference/projects/actualthing.rst | 18:20 |
| fungi | oh, yeah i bet that's it | 18:20 |
| dansmith | and that seemed to work | 18:20 |
| gmann | which one you want to remove :) | 18:20 |
| fungi | i think one or more of the sphinx extensions generates rst files in the source tree | 18:20 |
| dansmith | eww | 18:21 |
| fungi | we should probably add a rm to tox.ini to clear those and the build tree in testenv:docs | 18:21 |
| fungi | .gitignore includes reference/projects/*.rst | 18:22 |
| fungi | so presumably those can all be cleared safely | 18:22 |
| opendevreview | Dan Smith proposed openstack/governance master: Propose release cadence adjustment resolution https://review.opendev.org/c/openstack/governance/+/828777 | 18:22 |
| fungi | i'll propose a patch | 18:22 |
| dansmith | fungi: I can do it, I have it right here | 18:23 |
| fungi | oh, go for it | 18:23 |
| fungi | looks like reference/projects/index.rst should not be removed as it's a tracked file | 18:23 |
| fungi | so might not be as simple as a straight rm | 18:23 |
| dansmith | oh sure, NOW you tell me :P | 18:24 |
| fungi | when i git clean, that's the only file left in the reference/projects dir | 18:24 |
| fungi | maybe this could be made easier to clean though with some minor adjusting | 18:25 |
| dansmith | is it generated? | 18:25 |
| dansmith | my tree shows clean after doing that | 18:25 |
| dansmith | er, hmm, maybe not | 18:26 |
| fungi | reference/projects/index.rst looks not-generated, it contains a title and a couple of parahraphs, and then a toctree for * | 18:26 |
| dansmith | yah | 18:26 |
| fungi | though i suppose it *could* be put somewhere else and then copied to that dir when the projects are built | 18:27 |
| fungi | or whatever builds those files could be made to remove everything it finds there except index.rst | 18:28 |
| fungi | _write_team_pages() in doc/source/_exts/teams.py would probably be a good place to add that logic | 18:29 |
| opendevreview | Dan Smith proposed openstack/governance master: Clean generated files before run in docs target https://review.opendev.org/c/openstack/governance/+/828780 | 18:31 |
| dansmith | fungi: that okay/ | 18:31 |
| fungi | yep, that'll work | 18:32 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!