Tuesday, 2024-04-30

opendevreviewGhanshyam proposed openstack/governance master: Add timeline to remove enforce_scope in RBAC goal  https://review.opendev.org/c/openstack/governance/+/91517902:51
opendevreviewGhanshyam proposed openstack/governance master: Move distributed-project-leadership model into doc  https://review.opendev.org/c/openstack/governance/+/91682202:55
opendevreviewGhanshyam proposed openstack/governance master: Add DPL model & liaison reset policy  https://review.opendev.org/c/openstack/governance/+/91683303:24
opendevreviewGhanshyam proposed openstack/governance master: Add TC liaison in DPL model implementation  https://review.opendev.org/c/openstack/governance/+/91751603:43
opendevreviewhongbin proposed openstack/governance master: Move openstack/kuryr and openstack/kuryr-libnetwork to Zun  https://review.opendev.org/c/openstack/governance/+/91751703:56
*** zbitter is now known as zaneb08:09
opendevreviewJames Page proposed openstack/governance master: Retire all single charm repositories  https://review.opendev.org/c/openstack/governance/+/90349009:53
opendevreviewJames Page proposed openstack/governance master: Retire all single charm repositories  https://review.opendev.org/c/openstack/governance/+/90349010:35
*** ustrin_ is now known as ustrin11:20
opendevreviewJames Page proposed openstack/governance master: Retire all single charm repositories  https://review.opendev.org/c/openstack/governance/+/90349013:36
*** geguileo is now known as Guest271316:12
*** Guest2713 is now known as geguileo16:12
timburkefrickler, huh. i'm more confused than ever about how to "close" a feature branch. i was hoping that the stable->unmaintained patches might act as something of a guide, but then i realized that they're purely additive -- the actual deletion of the stable branch is done manually, i take it? so i could propose something to tag a bunch of "feature/<topic>/closed" tags or something, but it'd still require some manual 17:06
timburkeintervention to get everything resolved17:06
timburkei also notice, though, that we're got some feature branches that don't have entries under deliverables (feature/sp-review, feature/crypto, feature/crypto-review, feature/hummingbird, feature/repconn) and they *don't* appear on https://zuul.opendev.org/t/openstack/config-errors?project=openstack%2Fswift&skip=0&limit=10017:06
timburkewould it work to just delete the branch entries from the various deliverables files and *skip* deleting the branches in git?17:07
JayFtimburke: when Ironic has been in similar situations w/r/t our bugfix/ branches, we had to adjust project-config to allow branch deletion and do it manually with git client17:11
JayFtimburke: (until we recently added support for this to releases automation)17:12
timburkei mean, i don't actually *care* about whether the branch gets deleted or not -- they're just stale and popping zuul config errors, which seems to be bugging somebody. if we could have them just get ignored, that'd be great. if we delete them, that's fine -- as long as we've got a tag for where they were at the point of deletion. if the tag is named the same as the old branch, that'd be ideal :-)17:16
JayFYeah, for Ironic w/bugfix branches, we had to perform those kind of activities manually after getting permissions addressed in project-config. I'm unsure if there's another route to do it.17:19
JayFhttps://etherpad.opendev.org/p/IronicBugfixBranchCleanup + https://etherpad.opendev.org/p/IronicBugfixBranchCleanupRFR are my notes from then17:21
JayFI am unsure it's useful, but there they are :D 17:21
timburkethanks17:25
JayFwe had to enable access to these branches in project-config, too17:26
JayFit's likely still in the master version of perms for ironic17:26
fricklerwe can't just ignore specific branches in zuul afaik. the entries in the deliverables files are not relevant for that, it is the existence of these branches in gerrit17:30
fricklerthe deletion of old stable/unmaintained branches is done semi automated by a tool that checks the xyz-eol/-eom tags. I'm not sure about the details of what ironic has done17:32
fricklerbut you might be able to adapt that once you update your gerrit ACL to allow you to do feature/* branch deletions17:34
fricklerthe issue with the zuul config errors in general is that there are so many of them, obfuscating the view to those of them that do actually matter17:34
fricklerso the TC has tried to push projects to clean those up in order to make the work of maintaining the CI easier for the community as a whole17:35
timburkeah... and those old branches predate the existence of .zuul.yaml in swift...17:37
JayFYeah, I suspect you'll have to go the Ironic route: setup the ACLs then manual removal17:40
JayFat a minimum, that path will work and get you outta this, versus some unknown path with release tooling :)17:40
fricklerwell if a branch has no zuul config, there also should be no error. the errors I see almost all come from actual references to centos-7 which is no longer available17:58
timburkelet's see what CI does with https://review.opendev.org/c/openstack/releases/+/917781 :-)18:16
opendevreviewMerged openstack/governance master: Appoint Wenxiang Wu as PTL of Skyline  https://review.opendev.org/c/openstack/governance/+/91510822:57

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!