| prometheanfire | hmm, looks like urwid updates are hitting gertty too now | 05:17 |
|---|---|---|
| priteau | Hello. It seems that I don't have core reviewers privileges on blazar:unmaintained/yoga, unlike all other branches. Is this the right place to ask? | 15:03 |
| fungi | priteau: see https://governance.openstack.org/tc/resolutions/20231114-amend-unmaintained-status.html | 15:08 |
| frickler | priteau: tldr: this is intentional, maintainance for the "unmaintained" branches is to be done by a dedicated team different from the normal project teams | 15:10 |
| fungi | in particular, the goal is to make sure that project contributors don't feel like it's their responsibility to care about those branches | 15:11 |
| frickler | yes, that's the main motivation for that setup | 15:12 |
| priteau | And this how we should create a group? https://review.opendev.org/c/openstack/project-config/+/902796 | 15:22 |
| frickler | priteau: well you don't need to unless you want to specifically contribute to only the unmaintained branches of a single project | 15:26 |
| frickler | you can also leave things to the openstack-unmaintained-core team ... or apply to join that team | 15:26 |
| priteau | It was specifically for blazar, I doubt anyone else will review its patches. But I might propose to just EOL Yoga instead. | 15:27 |
| frickler | moving to eol is another option of course, yes | 15:28 |
| fungi | in fact, with the new process you don't need to propose eol. branches switch from stable (maintained) to unmaintained for one cycle. if nobody expresses an interest in keeping them open, then they go to eol automatically. someone has to ask to keep branches in unmaintained state if you want to continue to have patches merge to them | 15:35 |
| fungi | once nobody cares enough about an unmaintained branch to ask to keep it open, it will be closed at the start of the next development cycle | 15:36 |
| priteau | What about all the .gitreview patches that were automatically proposed by bot? Will the unmaintained group merge them or will they stay open until EOL? | 15:37 |
| fungi | i think that's undecided still? the way things are written now, if nobody has an interest in merging changes to those branches, they'll be deleted when the branch goes eol | 15:38 |
| priteau | It's really what prompted me to look into why I couldn't +2 the patch | 15:39 |
| fungi | also the .gitreview change is only relevant if someone's going to propose more changes to the branch anyway | 15:40 |
| fungi | priteau: probably worth asking the folks listed in https://review.opendev.org/admin/groups/openstack-unmaintained-core,members what their intentions are with those. so elodilles and tonyb at the moment | 15:42 |
| clarkb | my recommendation would be that any merges, including the .gitreview updates, be handled by volunteers to care for the unmaintained branches. The reason for this is that you may need to make other edits before the .gitreview change is mergeable | 15:50 |
| clarkb | and yes you can still push to gerrit even without an updated .gitreview file in the repo. You can either push explicitly or keep a local edit of the file | 15:50 |
| frickler | one thing that is an issue though is that things like periodic jobs got cloned from stable/yoga and people don't want images to be built and pushed to registries for the unmaintained branches, so "leave it untouched" isn't a good option there | 15:54 |
| frickler | see https://review.opendev.org/c/openstack/kolla/+/908251 as an example | 15:55 |
| clarkb | yes I think zuul envisioned that branches would be culled if no longer needed rather than simply renamed | 15:56 |
| fungi | it's the "if no longer needed" part that the new process tries to answer, unfortunately | 15:57 |
| fungi | my proposal was in fact exactly that (just eol/delete them at the end of normal maintenance), but was unpopular with the audience at that forum session | 16:00 |
| clarkb | in order to have the benefits of a strong CI system at the pointy end of the spear where people are focused we need tooling and that tooling needs care. Once it drops back to the "we don't care anymore" point we end up with the struggle here | 16:01 |
| fungi | the primary objection was "but someone might still want to help maintain it" | 16:01 |
| clarkb | fungi: ya I'm with you fwiw. But there is always the hope someone will come along and do more work and we're afraid of interrupting that possibility | 16:01 |
| frickler | elodilles: one question related to the above: iiuc you want to keep victoria open, which would also mean keeping all later branches open. do you target a very specific set of projects or essentially all of them? | 16:01 |
| elodilles | frickler: well, core projects definitely, though for sake of simplicity we can try to start with all of them, otherwise we don't know what we kill with an EOL'd project if that turns out needed for some jobs | 16:08 |
| elodilles | frickler: now i started to review the .gitreview patches as the 'pinning tox' fix made the gate passing for those patches | 16:09 |
| elodilles | btw, thanks for that | 16:09 |
| elodilles | i've +2+W'd a couple of patches, let's see if the gate really works on them | 16:10 |
| priteau | Thanks elodilles | 16:10 |
| elodilles | priteau: np | 16:10 |
| opendevreview | Lajos Katona proposed openstack/project-config master: unmaintained: gerritbot notification for Networking https://review.opendev.org/c/openstack/project-config/+/908606 | 16:46 |
| JayF | o/ can someone please seed me into https://review.opendev.org/admin/groups/338621b254db5f73639b981241df483b5d761495,members | 18:20 |
| JayF | or really, seed ironic-core into it if possible | 18:26 |
| JayF | (final state is going to be ironic-core + openstack-unmaintained-core) | 18:26 |
| fungi | JayF: done | 18:27 |
| JayF | thanks! Looks like I was able to populate it | 18:29 |
| fungi | awesome, lmk if you need anything else | 18:30 |
| opendevreview | Jay Faulkner proposed openstack/project-config master: ironic-unmaintained-core access to all Ironic proj https://review.opendev.org/c/openstack/project-config/+/908647 | 18:48 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!