| *** ralonsoh_ is now known as ralonsoh | 08:04 | |
| elodilles | tonyb: i was on PTO (i forgot to change my nick to elodilles_pto :S) but now i commented on your patch | 08:49 |
|---|---|---|
| elodilles | rosmaita: sorry, I was on PTO. let me know if the question is still relevant o:) | 08:50 |
| frickler | elodilles: welcome back ;) regarding the unmaintained transition: would you also be interested in checking the CI status for the older branches and refreshing the opt-in status for them? at least it would be great if that part could be handled by the unmaintained team themselves, so neither me nor the TC need to deal with it | 09:59 |
| tonyb | frickler: what are you requesting? something like a noop job for all projects with an unmaintained branch to loosely check the if CI works or not? | 10:09 |
| tonyb | something else? | 10:09 |
| frickler | tonyb: there are two clauses in https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html that I would like to see followed: | 10:11 |
| frickler | "By default, only the latest eligible Unmaintained branch is kept. When a new branch is eligible, the Unmaintained branch liaison must opt-in to keep all previous branches active." | 10:11 |
| frickler | "The CI for all branches must be in good standing at the time of opt-in." | 10:11 |
| frickler | how exactly that is done I don't care. current status is that nothing happens unless someone takes some action. I've kind of done checks myself in previous cycle, but I'd prefer if the people interested in keeping branches alive could do that themselves | 10:12 |
| frickler | like we have zuul config errors for older unmaintained branches that exist for years and nobody has taken care of them despite promises that were made | 10:14 |
| elodilles | frickler: hi o/ i'll try to do that, probably starting with moving 2024.1 Caracal to unmaintained as soon as possible ;) i'll see how my timing will allow things as you know this week is PTG + i have some downstream errands to run as well | 10:27 |
| tonyb | frickler: fair enough. the whole unmaintained thing happened while I was paying less attention. I didn't notice that we're only supposed to keep one around by default. | 10:42 |
| tonyb | I'll script up some ci tests this week, and think about the opt-in process | 10:43 |
| rosmaita | elodilles: hope you had some good PTO ... question got resolved, but thanks for following up, i should have cancelled it! | 12:11 |
| rosmaita | elodilles: although, just so you're aware, i posted glance releases for E,D,and C and rebased your "C goes unmaintained" patch on them: https://review.opendev.org/c/openstack/releases/+/963608 | 12:19 |
| elodilles | rosmaita: ACK, thanks for the rebase, i'll review the release patches ASAP | 12:20 |
| rosmaita | thanks! | 12:20 |
| opendevreview | Elod Illes proposed openstack/releases master: [neutron] Transition 2024.1 Caracal to Unmaintained https://review.opendev.org/c/openstack/releases/+/963594 | 13:03 |
| elodilles | release-team: hi o/ may i get some reviews for nova and glance release patches, especially for caracal ones, so that we can move forward with the Caracal to Unmaintained transition? thanks in advance o/ | 13:07 |
| ttx | looking | 14:11 |
| ttx | SHould be all set | 14:15 |
| opendevreview | Merged openstack/releases master: [glance] October 2025 Epoxy release https://review.opendev.org/c/openstack/releases/+/964240 | 14:25 |
| opendevreview | Merged openstack/releases master: [glance] October 2025 Dalmatian release https://review.opendev.org/c/openstack/releases/+/964241 | 14:25 |
| opendevreview | Merged openstack/releases master: [glance] Final Caracal releases https://review.opendev.org/c/openstack/releases/+/964227 | 14:26 |
| opendevreview | Merged openstack/releases master: nova: Release 2025.2 Flamingo 32.1.0 https://review.opendev.org/c/openstack/releases/+/964468 | 14:29 |
| opendevreview | Merged openstack/releases master: nova: Release 2025.1 Epoxy 31.2.0 https://review.opendev.org/c/openstack/releases/+/964469 | 14:29 |
| opendevreview | Merged openstack/releases master: nova: Release 2024.2 Dalmatian 30.2.0 https://review.opendev.org/c/openstack/releases/+/964470 | 14:29 |
| opendevreview | Merged openstack/releases master: nova: Release 2024.1 Caracal 29.4.0 https://review.opendev.org/c/openstack/releases/+/964471 | 14:29 |
| elodilles | thanks o/ | 15:12 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: Create new puppet-ceph release https://review.opendev.org/c/openstack/releases/+/964890 | 15:25 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: Create new puppet-ceph release https://review.opendev.org/c/openstack/releases/+/964890 | 15:46 |
| elodilles | tkajinam: is this ready to go? (see my question on the patch) -> https://review.opendev.org/c/openstack/releases/+/964226 | 16:04 |
| tkajinam | elodilles, yes that one is ready | 16:04 |
| elodilles | ACK, thanks, then i'm adding back +W | 16:04 |
| tkajinam | I'm merging metadata update of puppet-ceph so that we can release it too shortly | 16:05 |
| elodilles | sorry for not reviewing it earlier (last week was a rather short work week to me) | 16:05 |
| elodilles | tkajinam: ACK, will keep an eye on it | 16:05 |
| tkajinam | no problem. we are not really in hurry about it, due to no 2025.2 release by rdo :-( | 16:05 |
| elodilles | :-o | 16:07 |
| elodilles | i guess RDO is not interested in non-SLURP releases? :-o | 16:08 |
| elodilles | release-team: we have a release job failure, but i think we are mostly good as tagging was finished properly and the package is on pypi, "only" the reno update job was timed out -> publish-openstack-releasenotes-python3 https://zuul.opendev.org/t/openstack/build/825d6712e84745a48bd4f920a7c1705b : TIMED_OUT in 1h 00m 41s | 16:13 |
| tkajinam | I'm not following the full discussion but I think the most problematic point is that we have to migrate to c10s due to removal of Python 3.9 | 16:13 |
| elodilles | oh, so it's more like a tooling issue then | 16:16 |
| tkajinam | yeah that'd be true | 16:17 |
| opendevreview | Merged openstack/releases master: Puppet OpenStack 2025.2 release https://review.opendev.org/c/openstack/releases/+/964226 | 16:38 |
| frickler | weird, zuul says "This build does not provide any results", but I do see them behind the "logs" link | 16:50 |
| clarkb | frickler: did the job timeout? | 16:51 |
| clarkb | there is a bug in a change I wrote recently due to inaddequate testing. I have a fix proposed. But basically we're trying to include info about time outs and other failures in the job-output.json file and it didn't supply enough info for the web ui to render thinsg from the json | 16:52 |
| frickler | yes, I'm talking about the reno update elod mentioned above | 16:52 |
| clarkb | it only affects jobs with these exceptional failures (normal failures are unaffected) and should be fixed soon I hope | 16:52 |
| clarkb | when I tested the json edits I injected the edited json a level below where the web ui first reads it so didn't notice that the level above would fail | 16:53 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!