noonedeadpunk | elodilles: hey! I need some guidance on how to EOL some projects, there were not automated on creation | 08:16 |
---|---|---|
noonedeadpunk | like openstack/openstack-ansible-ops, openstack/openstack-ansible-os_cloudkitty, openstack/openstack-ansible-os_congress, openstack/openstack-ansible-os_monasca, openstack/openstack-ansible-os_monasca-agent, openstack/openstack-ansible-os_panko, openstack/openstack-ansible-os_tacker and openstack/openstack-ansible-tests :) | 08:18 |
elodilles | i guess you mean the older branches that are EOL'd ages ago, like queens, pike, ocata | 08:23 |
elodilles | the cause why they are not EOL'd with the other repos is that they were not registered in opnestack/releases under deliverables/* | 08:25 |
elodilles | hence we were not aware that they are there | 08:25 |
elodilles | there is no official way yet how to delete them (other than manually, which we don't do... (yet)) | 08:28 |
elodilles | noonedeadpunk: ^^^ | 08:28 |
noonedeadpunk | elodilles: well, I see... So the tricky thing is - then I need to fix them, as they contain errors in zuul configuration. | 08:29 |
noonedeadpunk | Which isn't smth I'd love to invest time into | 08:29 |
noonedeadpunk | So they make troubles for infra | 08:30 |
noonedeadpunk | Maybe I can just replace all jobs with noop there and backport that... | 08:30 |
noonedeadpunk | but ugh | 08:30 |
frickler | wouldn't it be possible to give PTLs temporary permissions on gerrit to clean those up manually if they volunteer to do so? | 08:30 |
frickler | like was done in earlier times? | 08:31 |
noonedeadpunk | I'd rather do that then fix them ^ | 08:31 |
elodilles | could work, but people have to be very careful / decide to have proper EOL tags or lose history, etc | 08:33 |
frickler | yes, that's how work looked like in the previous millenium ;) and technically I'd say those branches still belong to that period | 08:36 |
opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: [OpenStackAnsible Roles] Transition Stein to End of Life https://review.opendev.org/c/openstack/releases/+/894283 | 08:44 |
noonedeadpunk | elodilles: on other topic - I've attempted to produce EOL for osa roles ^ | 08:45 |
elodilles | noonedeadpunk: thanks \o/ | 08:54 |
*** ykarel|away is now known as ykarel | 09:18 | |
opendevreview | Yasufumi Ogawa proposed openstack/releases master: Add Tacker Bobcat cycle highlights https://review.opendev.org/c/openstack/releases/+/894293 | 10:30 |
opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible Antelope https://review.opendev.org/c/openstack/releases/+/893534 | 12:55 |
noonedeadpunk | would be awesome to land that sooner then later ^ | 13:02 |
hberaud | Meeting will start in minutes | 13:53 |
elodilles | ~o~ | 13:57 |
hberaud | #startmeeting releaseteam | 14:00 |
opendevmeet | Meeting started Fri Sep 8 14:00:01 2023 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
opendevmeet | The meeting name has been set to 'releaseteam' | 14:00 |
hberaud | ping elodilles armstrong | 14:00 |
hberaud | Meet you at line 389 => https://etherpad.opendev.org/p/bobcat-relmgt-tracking | 14:00 |
elodilles | o/ | 14:00 |
hberaud | Thierry is traveling so I don't think we will see him today | 14:01 |
hberaud | so let's go | 14:01 |
hberaud | #topic Review task completion | 14:01 |
hberaud | 1. Process any remaining client library freeze exception | 14:01 |
hberaud | https://review.opendev.org/q/topic:bobcat-milestone-3+is:open | 14:01 |
hberaud | 3 patches remains opened because as you said (elodilles) their gates are broken | 14:02 |
hberaud | We didn't get feedback from PTLs | 14:02 |
elodilles | :S | 14:02 |
hberaud | 2 patches are even without PTLs' votes | 14:02 |
diablo_rojo | o/ | 14:02 |
hberaud | What can we do here? The problem is on the deliverable side and not on our side, so... | 14:02 |
diablo_rojo | Which PTLs? | 14:02 |
diablo_rojo | err projects? | 14:02 |
diablo_rojo | I can try to poke at them. | 14:02 |
hberaud | barbican, murano, and sahara | 14:03 |
hberaud | for those patches https://review.opendev.org/q/topic:bobcat-milestone-3+is:open | 14:03 |
hberaud | thanks diablo_rojo | 14:03 |
elodilles | with a quick check i see that python-saharaclient's gate was fixed (at least what i see) | 14:03 |
fungi | yeah, it can also be brought to the attention of the tc | 14:03 |
elodilles | (so python-saharaclient's patch can be updated at least) | 14:04 |
diablo_rojo | I can poke at Barbican and Murano if you'd like, otherwise the TC yeah. | 14:04 |
hberaud | ah yes | 14:04 |
elodilles | we have to ping requirements team (via ML) anyway, with RFE's regarding these 3 releases, right? | 14:05 |
opendevreview | Hervé Beraud proposed openstack/releases master: Release final python-saharaclient for 2023.2 Bobcat https://review.opendev.org/c/openstack/releases/+/892957 | 14:05 |
hberaud | I updated the SHA ^ | 14:06 |
elodilles | ++ | 14:06 |
hberaud | elodilles: as the deadline is behind us, I think that yes | 14:06 |
hberaud | #action diablo_rojo to ping the sahara and the barbican team about the broken gates | 14:07 |
elodilles | well, i'm hesitant between pushing through the releases anyway (as we did last week with non-client libs) or wait for gate fixes / team responses | 14:08 |
diablo_rojo | I will get on that right now :) | 14:08 |
elodilles | thanks diablo_rojo o/ | 14:08 |
hberaud | thx | 14:08 |
diablo_rojo | elodilles: nor Murano? | 14:08 |
diablo_rojo | *not | 14:08 |
elodilles | OK, then let's wait a bit, and we can get back to it on Monday | 14:08 |
hberaud | elodilles: I'd suggest to wait early monday and if the things are still stuck, I'd suggest to push through, thoughts? | 14:09 |
hberaud | wfm | 14:09 |
hberaud | you beat me | 14:09 |
elodilles | hberaud: sounds like a plan | 14:09 |
elodilles | :) | 14:09 |
elodilles | diablo_rojo: you meant hberaud :) and yes, barbican & murano o:) | 14:10 |
diablo_rojo | elodilles: yes I did lol | 14:10 |
* diablo_rojo has had no caffeine this morning | 14:10 | |
elodilles | and you are still awake?! :-o magic!!! :-o | 14:11 |
elodilles | :) | 14:11 |
hberaud | I added a related line for the next week tasks | 14:11 |
diablo_rojo | Its painful and flawed. | 14:11 |
elodilles | hberaud: thx \o/ | 14:11 |
hberaud | ok move on | 14:11 |
hberaud | 2. Early in the week, email openstack-discuss list to remind PTLs that cycle-highlights are due this week so that they can be included in release marketing preparations | 14:12 |
hberaud | https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034959.html | 14:12 |
hberaud | and AFAIK I see many related patches submitted after that | 14:12 |
elodilles | yepp, cycle higlights patches have been arriving during the week, so ++ | 14:12 |
diablo_rojo | Yayayayay | 14:13 |
hberaud | 3. Freeze all cycle-based library releases except for release-critical bugs. Independently-released libraries may still be released, but constraint or requirement changes will be held until after the freeze period | 14:13 |
hberaud | Do you noticed things like that? ^ | 14:13 |
elodilles | nope | 14:13 |
hberaud | I think oslo patches will arrive soon | 14:14 |
fungi | speaking of critical bugs, there's been more upheaval in the oslo.messaging security bug, seems like the fix caused a regression so another change and new release on stable/2023.2 is likely | 14:14 |
elodilles | but we will have the above mentioned 3 client lib | 14:14 |
hberaud | as we discussed about that on the oslo channel | 14:14 |
elodilles | oh, good to know O.o | 14:14 |
frickler | also some set of reqs bumps might still be open for recently released libs | 14:15 |
hberaud | ack | 14:15 |
frickler | there were a couple of merge conflicts | 14:15 |
frickler | and two libs are failing cross testing | 14:15 |
hberaud | which ones? | 14:15 |
frickler | castellan and oslo.db | 14:15 |
frickler | even oslo.db 13.1.0 is failing. not to speak of 14.0.0 | 14:16 |
hberaud | ugh | 14:16 |
hberaud | lets continue to discuss about that on the oslo channel | 14:17 |
frickler | https://review.opendev.org/c/openstack/requirements/+/883141 and https://review.opendev.org/c/openstack/requirements/+/887261 | 14:17 |
hberaud | thanks | 14:18 |
diablo_rojo | ftr, I have now reached out to those 3 PTLs | 14:18 |
hberaud | ack thx | 14:18 |
elodilles | I think we should track oslo.db & castellan issues as well next week, to get it sorted out as soon as possible :S | 14:20 |
hberaud | yeah | 14:20 |
hberaud | let me add it to our agenda | 14:20 |
hberaud | done | 14:22 |
elodilles | thanks ++ | 14:22 |
hberaud | ok next task | 14:22 |
hberaud | 4. Propose stable/$series branch creation for all client and non-client libraries that had not requested it at freeze time | 14:22 |
hberaud | https://review.opendev.org/q/topic:bobcat-stable-branches | 14:22 |
elodilles | i went through the still open patches earlier today and all look fine to me. +2'd & PTL-Approved+1'd them. | 14:23 |
hberaud | I'll merge all the remaining patches after the meeting | 14:23 |
elodilles | ++ | 14:23 |
hberaud | so this point seems in good shape | 14:24 |
hberaud | 5. List cycle-with-intermediary deliverables that have not been refreshed in the last 2 months and send a separate email targeted to teams with such old deliverables to remind them to release (if needed) otherwise a probably outdated version will be used for the final release | 14:24 |
hberaud | https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034973.html | 14:24 |
hberaud | so only the QA team was listed in this mail and they replied, so I think this topic is on the rails | 14:25 |
elodilles | ++ | 14:25 |
hberaud | thanks gmann | 14:25 |
hberaud | and that's all for the weekly tasks | 14:26 |
hberaud | #topic Assign next week tasks | 14:26 |
elodilles | all taken as i see \o/ | 14:27 |
hberaud | thanks elodilles for putting your name | 14:27 |
hberaud | \o/ | 14:27 |
hberaud | #topic Review countdown email | 14:27 |
hberaud | https://etherpad.opendev.org/p/relmgmt-weekly-emails | 14:28 |
elodilles | looks good! | 14:28 |
hberaud | thx | 14:28 |
hberaud | and sent | 14:30 |
hberaud | #topic Open Discussion | 14:30 |
hberaud | Anything else that you want to discuss today? | 14:30 |
frickler | maybe a short question about branch cleanup | 14:31 |
frickler | what we discussed earlier with noonedeadpunk about deleting old branches predating release automation | 14:31 |
frickler | do you think you could grant deletion powers in gerrit to volunteering ptls? or would that have to be a TC decision? | 14:32 |
elodilles | it's an project-config (infra) change anyway | 14:32 |
frickler | on the technical side, yes, my question is more about policy | 14:33 |
hberaud | then if this is a policy change I'd argue that's a TC decision | 14:33 |
fungi | ultimately, the tc can authorize granting permission for that | 14:33 |
opendevreview | Merged openstack/releases master: [blazar] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893626 | 14:34 |
fungi | for clear separation of concerns, it would probably be best as an acl change to the specific projects affected rather than openstack-wide | 14:34 |
frickler | maybe the release team already has the permission to delegate this | 14:34 |
elodilles | fungi: sounds good to me | 14:34 |
frickler | but I think we can create a change in project-config and then ask TC for feedback | 14:35 |
hberaud | fungi: +1 | 14:35 |
elodilles | frickler: it's more like what fungi says | 14:35 |
elodilles | frickler: i mean, not a single change, but a specific change for a specific project | 14:36 |
elodilles | but yes | 14:36 |
frickler | yes, we only have one volunteer so far, so that's fine | 14:36 |
elodilles | ++ | 14:37 |
opendevreview | Merged openstack/releases master: [zun] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893645 | 14:37 |
frickler | I'll check who else could get involved in the things blocking global job cleanup | 14:37 |
fungi | i'm assuming noonedeadpunk is only volunteering to be responsible for deleting old branches of deliverables for a specific team, not across all of openstack | 14:37 |
frickler | yes, that was for osa repos | 14:37 |
frickler | ok, that's fine then for me, thx | 14:38 |
hberaud | anything else? | 14:39 |
elodilles | nothing from me | 14:39 |
hberaud | Then I think we are done! | 14:41 |
hberaud | thanks everyone! | 14:41 |
hberaud | #endmeeting | 14:41 |
opendevmeet | Meeting ended Fri Sep 8 14:41:06 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:41 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-09-08-14.00.html | 14:41 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-09-08-14.00.txt | 14:41 |
opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-09-08-14.00.log.html | 14:41 |
opendevreview | Merged openstack/releases master: [trove] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893643 | 14:41 |
opendevreview | Merged openstack/releases master: [senlin] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893642 | 14:41 |
elodilles | thanks hberaud | 14:41 |
opendevreview | Merged openstack/releases master: [manila] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893640 | 14:42 |
opendevreview | Merged openstack/releases master: [tacker] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893620 | 14:45 |
opendevreview | Merged openstack/releases master: [octavia] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893621 | 14:45 |
opendevreview | Merged openstack/releases master: [adjutant] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893625 | 14:47 |
frickler | hberaud: fyi there are still some more patches open on reqs master. did I understand things correctly that these are not affected by the freeze assuming they pass all testing? https://review.opendev.org/q/project:openstack/requirements+status:open+topic:new-release+branch:master | 14:47 |
opendevreview | Merged openstack/releases master: [monasca] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893630 | 14:47 |
opendevreview | Merged openstack/releases master: [designate] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893636 | 14:47 |
opendevreview | Merged openstack/releases master: [cinder] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893617 | 14:47 |
opendevreview | Merged openstack/releases master: [cyborg] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893637 | 14:47 |
opendevreview | Merged openstack/releases master: [ironic] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893611 | 14:47 |
opendevreview | Merged openstack/releases master: [magnum] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893639 | 14:47 |
opendevreview | Merged openstack/releases master: [keystone] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893614 | 14:47 |
opendevreview | Merged openstack/releases master: [mistral] Create 2023.2 branch for client and non-client libs https://review.opendev.org/c/openstack/releases/+/893629 | 14:48 |
noonedeadpunk | Well, I can tag/drop for other projects, if there's a list of leftovers | 14:49 |
noonedeadpunk | It's not time-consuming thing if what needs to be done is already defined | 14:49 |
noonedeadpunk | But from standpoint of what would make more sense is that PTL's be responsible of that, not to give too broad permissions in gerrit to individuals outside of releases/infra roots | 14:50 |
opendevreview | Sylvain Bauza proposed openstack/releases master: Nova 2023.2 Bobcat cycle highlights https://review.opendev.org/c/openstack/releases/+/894213 | 15:43 |
noonedeadpunk | was.... have cycle highlights deadline expired on september 1? | 16:31 |
noonedeadpunk | checking if it's worth posting them or it's kinda useless at this point of time | 16:36 |
frickler | noonedeadpunk: the countdown mail just sent says "Finally, now is a good time to finalize release highlights." | 17:09 |
opendevreview | Jon Bernard proposed openstack/releases master: Cinder team releases for stable/2023.1 https://review.opendev.org/c/openstack/releases/+/893793 | 18:36 |
opendevreview | Jon Bernard proposed openstack/releases master: Cinder team releases for stable/zed https://review.opendev.org/c/openstack/releases/+/893794 | 18:36 |
opendevreview | Jon Bernard proposed openstack/releases master: Cinder team releases for stable/yoga https://review.opendev.org/c/openstack/releases/+/893795 | 18:36 |
opendevreview | Jay Faulkner proposed openstack/releases master: Ironic cycle highlights for 2023.2 https://review.opendev.org/c/openstack/releases/+/894228 | 19:30 |
opendevreview | Brian Rosmaita proposed openstack/releases master: [doc] fix typos in Caracal schedule https://review.opendev.org/c/openstack/releases/+/894394 | 20:26 |
opendevreview | Jake Yip proposed openstack/releases master: Add Magnum cycle highlights https://review.opendev.org/c/openstack/releases/+/894404 | 23:53 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!