Friday, 2021-07-16

*** odyssey4me is now known as Guest94501:22
*** rlandy|bbl is now known as rlandy01:49
*** odyssey4me is now known as Guest95501:53
*** ykarel|away is now known as ykarel04:31
*** chandankumar is now known as chkumar|rover05:21
*** iurygregory_ is now known as iurygregory06:38
*** rpittau|afk is now known as rpittau07:31
*** dmellado_ is now known as dmellado07:41
opendevreviewVishal Manchanda proposed openstack/project-config master: Retire django-openstack-auth  https://review.opendev.org/c/openstack/project-config/+/80045908:07
*** bhagyashris_ is now known as bhagyashris|ruck08:24
*** ykarel is now known as ykarel|lunch09:06
*** odyssey4me is now known as Guest101109:20
opendevreviewMatthias Runge proposed openstack/project-config master: Enable deleting left-overs of panko deprecation  https://review.opendev.org/c/openstack/project-config/+/80024109:56
*** odyssey4me is now known as Guest102510:06
*** ykarel|lunch is now known as ykarel11:11
opendevreviewTristan Cacqueray proposed openstack/project-config master: gerritbot: add matrix configuration  https://review.opendev.org/c/openstack/project-config/+/80106313:52
opendevreviewTakashi Kajinami proposed openstack/project-config master: tripleo-common-tempest-plugin - Step 2: End project Gating  https://review.opendev.org/c/openstack/project-config/+/80015413:59
opendevreviewTakashi Kajinami proposed openstack/project-config master: tripleo-common-tempest-plugin - Step 4: Remove Project  https://review.opendev.org/c/openstack/project-config/+/80015713:59
*** rpittau is now known as rpittau|afk14:08
*** ykarel is now known as ykarel|away14:46
opendevreviewTristan Cacqueray proposed openstack/project-config master: gerritbot: add matrix configuration  https://review.opendev.org/c/openstack/project-config/+/80106314:59
opendevreviewTristan Cacqueray proposed openstack/project-config master: gerritbot: add matrix configuration  https://review.opendev.org/c/openstack/project-config/+/80106315:22
opendevreviewTristan Cacqueray proposed openstack/project-config master: gerritbot: add matrix configuration  https://review.opendev.org/c/openstack/project-config/+/80106315:33
opendevreviewMerged openstack/devstack-gate master: Moving IRC network reference to OFTC  https://review.opendev.org/c/openstack/devstack-gate/+/80013415:43
opendevreviewVishal Manchanda proposed openstack/project-config master: Retire django-openstack-auth  https://review.opendev.org/c/openstack/project-config/+/80045916:43
opendevreviewVishal Manchanda proposed openstack/project-config master: Retire django-openstack-auth  https://review.opendev.org/c/openstack/project-config/+/80053216:43
melwittI think I'm noticing that the launchpad bug update that used to change "Fix Committed"  to "Fix Released" after a release was done for the branch isn't happening anymore. it looks like it should be this https://opendev.org/opendev/jeepyb/src/branch/master/jeepyb/cmd/update_bug.py#L187-L18822:33
melwittdoes anyone have any idea how/why that might not be working right anymore?22:34
clarkbmelwitt: not off the top of my head. Though do we use proposed/* branches anymore?22:41
clarkbs/anymore/anywhere/22:41
melwittI am not familiar with the proposed/* thing, sorry22:41
melwittthat is why this part doesn't work anymore probably?22:41
clarkbya I think that was handling a very specific branch setup. I suspect that https://opendev.org/opendev/jeepyb/src/branch/master/jeepyb/cmd/update_bug.py#L180-L182 maybe the problem22:42
melwittif not, I'm not yet sure what we need to look for to signal a release happened22:42
melwittI _think_ that part works because I have seen bugs go to Fix Released on master branch fixes22:43
melwittwhat I find doesn't work is when a stable branch fix that is Fix Committed (merged but not released) becomes released (the openstack/releases patch merges), it does not change to "Fix Released" anymore and it used to22:43
clarkbah22:44
clarkbthen it is probably because that code doesn't handle stable/* branches only proposed/ and master22:44
clarkbI'm trying to remember what proposed/ was/is for and drawing a blank22:46
clarkbI double checked the delay-release flag and only some charms and a couple of x/ repos seem to set it22:48
melwittok, thanks clarkb I'll do some digging based on those tidbits22:55
melwittyeah delay-release flag is ok because the logic is "if (not p.is_delay_release(args.project)" which is true for everything, so that part is working fine22:57
melwittit's this proposed/* business that needs an update. just have to find to what22:57
clarkbI think you want it to also process on stable/* branches22:58
clarkbbut there is no stable/* condition22:58
melwittI think this proposed thing had to do with releases22:59
melwittmaybe releases used to get merged to a proposed/ branch or something22:59
melwittbecause we don't want to set Fix Released on a stable/branch bug fix until the release happens, not at patch merge time23:00
melwittoh but this is checking if it's Fix Committed23:01
clarkbthe gerrit events only fire when patches merge though23:01
clarkbif you want to wait until the release is tagged on the stable branch then you might need to use a different tool for that (somethin triggered by the release team's jobs/tools maybe)23:01
melwittyeah ... so that's why I keep thinking this was watching some kind of release patch process that used to be23:02
melwittI'll go back through my email and see what it used to look like, I can't remember if the "This issue was fixed in the openstack/nova N release." was co-located with the Fix Committed => Fix Released change or not23:03
clarkbIf it wasn't and you don't want ot change that then running some sort of updating as part of the release tooling makes sense23:06
clarkbseparately I think we're tryingto push more of that into zuul if we can then we don't need to rely on image updates on the gerrit side to make these changes too23:06
melwittyeah, I'm just not sure whether changing that string to "stable/" would cause things to get marked as Fix Released too early, I was thinking it would but I'm also tired so maybe I'm way off23:07
melwittack23:07
clarkbmelwitt: it would switch it at change merge time if the bug was already marked fix released23:08
melwittyeah.. it's weird because the first go round, it would mark the bug as Fix Committed for say, stable/train. so I can't imagine what patch-merged event would happen again related to the same bug23:10
melwitti.e. I am yet to understand how this used to work23:11
melwittbecause whatever this was saw a patch-merged event and was able to find the bug already in fix committed state and then change it to fix released23:11
clarkbmaybe there was some end of release dummy commit that set all the bug numbers on it that got merged once upon a time23:12
melwittyeah, I'm wondering that23:13
melwittinteresting https://review.opendev.org/q/branch:%255Eproposed.*23:13
melwittI'll look more at it later, curiosity23:14
melwitthave to run for now. thanks for the ideas o/23:15
clarkbgl!23:18

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