| *** amar7ibm is now known as amar7_ | 04:40 | |
| opendevreview | Merged openstack/nose-html-output master: docs: Update Freenode to OFTC https://review.opendev.org/c/openstack/nose-html-output/+/801256 | 06:45 |
|---|---|---|
| *** rpittau|afk is now known as rpittau | 07:07 | |
| *** odyssey4me is now known as Guest1488 | 08:33 | |
| *** odyssey4me is now known as Guest1498 | 11:38 | |
| *** xek_ is now known as xek | 12:27 | |
| *** rpittau is now known as rpittau|afk | 16:45 | |
| melwitt | clarkb: I took a try at updating launchpad Fix Released as part of a release script https://review.opendev.org/c/openstack/project-config/+/801376 | 20:32 |
| fungi | i likely missed discussion while on vacation, but were there lingering bugs related to the deferred release settings for the update-bug script? | 20:34 |
| melwitt | fungi: the bug I'm seeing (and I don't know how long ago this broke) is that when stable branches get a release, the infra user no longer updates them from "Fix Committed" to "Fix Released" and it used to | 20:39 |
| melwitt | everything else is working fine. master branch goes to "Fix Released" when a patch merges (a la continuous delivery) and stable branches get "Fix Committed" when a patch merges but has not yet been released in a point release | 20:41 |
| melwitt | what's broken is the stable branch Fix Committed => Fix Released transition when a stable branch is released containing that bug fix | 20:43 |
| melwitt | I spent time trying to ascertain when/why/how that functionality got broken but as clarkb pointed out, since it's related to releases it might be better to do such a thing in the release tooling instead (iiuc) | 20:44 |
| clarkb | melwitt: in this case better mostly because you can easily update those things without updating our deployments directly (which jeepyb requires) | 20:44 |
| clarkb | a logistics optimization :) | 20:45 |
| melwitt | ack, thanks for clarifying | 20:45 |
| melwitt | hehe | 20:45 |
| fungi | yeah, i thought that's what the delay-release option was supposed to do, basically set the series bugtasks to fix-committed and then the release managers switched them to fix-released at release time | 21:13 |
| fungi | though having the release automation do that part instead of a release manager of course makes sense | 21:14 |
| fungi | though i think maybe they settled for just leaving comments in the bugs, since a lot of projects configured update-bug to switch tasks to fix-released in master | 21:15 |
| fungi | maybe what's missing is that the stable branch maintainers were doing the same manual switching to fix-released for their series bugtasks but then stopped at some point? | 21:16 |
| melwitt | hm.. it's possible. I'll check my old launchpad emails to see if I can tell | 21:36 |
| melwitt | I could have sworn it was the infra user but maybe that's a false memory | 21:36 |
| melwitt | afaict it looks like you are right, how did I never notice this :( | 21:45 |
| fungi | doesn't mean it's not worth fixing! | 23:00 |
| fungi | but i agree that any automation which can be done in a zuul job instead of a gerrit hook is preferable | 23:01 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!