| *** elodilles_pto is now known as elodilles | 07:00 | |
| ttx | #startmeeting releaseteam | 13:00 |
|---|---|---|
| opendevmeet | Meeting started Fri Sep 27 13:00:08 2024 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| opendevmeet | The meeting name has been set to 'releaseteam' | 13:00 |
| ttx | Ping list: release-team elod armstrong | 13:00 |
| elodilles | o/ | 13:00 |
| frickler | \o | 13:00 |
| ttx | elodilles: o/ | 13:00 |
| ttx | frickler: o/ | 13:00 |
| ttx | #topic Review task completion | 13:00 |
| ttx | Process (Very) late RC1 releases (all) | 13:01 |
| ttx | So that was completed for Zun and Barbican team deliverables | 13:01 |
| elodilles | \o/ | 13:01 |
| ttx | The Kuryr deliverables that were not transferred to other teams remain blocked and should imho just not be released | 13:01 |
| elodilles | ACK | 13:02 |
| ttx | That is what https://review.opendev.org/c/openstack/releases/+/930554 clarified | 13:02 |
| ttx | although we might still want to cut a stable/2024.2 branch for kuryr-kubernetes for Tacker testing purposes | 13:02 |
| ttx | (we'll discuss that in open discussion) | 13:02 |
| elodilles | ++ | 13:03 |
| ttx | After all the projects enabled in devstack by default have been branched, we can engage with the (elod) | 13:03 |
| elodilles | yepp, so | 13:03 |
| elodilles | QA -> i've pinged the team, | 13:03 |
| elodilles | devstack and grenade have branched | 13:03 |
| elodilles | and the team started their release process | 13:04 |
| elodilles | so we should be on track with this | 13:04 |
| elodilles | I18n SIG -> i've sent a mail to I18n SIG chair (Ian) before the meeting | 13:05 |
| elodilles | according to their process guide ( https://docs.openstack.org/i18n/latest/release_management.html#projects-affecting-stringfreezes ), | 13:06 |
| elodilles | we probably are still OK, and the tooling can be updated for the new stable/2024.2 branch | 13:07 |
| elodilles | and last but not least: | 13:07 |
| elodilles | Requirements -> the branching patch has been proposed | 13:08 |
| elodilles | #link https://review.opendev.org/c/openstack/releases/+/930429 | 13:08 |
| elodilles | and merged | 13:08 |
| ttx | \o/ | 13:08 |
| ttx | Process any remaining stable branching exception (ttx) | 13:08 |
| ttx | That was also completed | 13:09 |
| ttx | #link https://review.opendev.org/q/topic:%22dalmatian-missing-stable-branches%22 | 13:09 |
| elodilles | sorry, one more thing for the prior task o:) | 13:09 |
| ttx | go for it | 13:10 |
| elodilles | prometheanfire tonyb : fyi, this can be announced: the requirements freeze is lifted from master :) | 13:10 |
| elodilles | ttx: that's all, sorry o:) | 13:11 |
| ttx | Notify the TC that it should be safe to apply the process to create the new release series landing pages for docs.openstack.org (elod) | 13:11 |
| elodilles | well, i created the patch series: https://review.opendev.org/q/topic:www-dalmatian-final | 13:11 |
| elodilles | and the first patch already merged | 13:12 |
| frickler | ah, still need to finish reviewing that | 13:12 |
| elodilles | frickler: project data is updated, so zuul gave Verified+1 now :] | 13:12 |
| frickler | yes, I wanted to check if there are other projects that can be dropped completely like openstack-chef | 13:13 |
| elodilles | hmmm, now i remember that we still need a site-map update patch that i promised | 13:13 |
| elodilles | frickler: good point, we can drop that from the template | 13:13 |
| elodilles | frickler: so that next time it won't appear at all | 13:13 |
| frickler | yes, that was my idea | 13:14 |
| elodilles | +1 | 13:14 |
| elodilles | (that's all i think) | 13:15 |
| ttx | On the day before the deadline for final release candidates, propose last-minute RCs where needed. (elod) | 13:16 |
| elodilles | sorry, i was on PTO yesterday and forgot to do this earlier :/ | 13:17 |
| elodilles | i've checked, and now i see that manila, | 13:17 |
| elodilles | and kolla team's deliverables need rc2 releases | 13:17 |
| elodilles | i'll generate them after the meeting | 13:18 |
| frickler | kolla is trailing, there shouldn't be an rc1 even? | 13:18 |
| elodilles | frickler: oh, right | 13:18 |
| elodilles | frickler: that explains why i saw that many patches | 13:18 |
| elodilles | o:) | 13:18 |
| ttx | yeah, kolla can wait | 13:18 |
| frickler | :) | 13:18 |
| elodilles | so then only manila needs a 2nd rc | 13:19 |
| ttx | so just manila? | 13:19 |
| ttx | ok let's processs it real quick after meeting so that they are all up | 13:19 |
| elodilles | ttx: ACK, will do | 13:19 |
| ttx | Send countdown email (ttx) | 13:19 |
| ttx | will do after meeting | 13:19 |
| ttx | After the email is sent, use propose-final-releases to tag the existing most recent release candidates as the final release for projects using the cycle-with-rc model. (elod) | 13:20 |
| ttx | we should do that once manila rc2 is processed | 13:20 |
| elodilles | yepp \o/ | 13:20 |
| elodilles | well | 13:20 |
| elodilles | i guess i can generate that after you've sent the mail, | 13:21 |
| elodilles | and just signal there that we need an update for manila's RC2 | 13:21 |
| ttx | elodilles: you could just build that patch on top of the manila rc2 patch | 13:21 |
| ttx | that way it includes it | 13:21 |
| elodilles | so that PTLs can see what is in progress | 13:21 |
| elodilles | ttx: +1 | 13:22 |
| ttx | #topic Assign R+0 week tasks | 13:22 |
| frickler | yes, otherwise we would lose reviews on the update | 13:22 |
| ttx | I have several meetings (including press interviews about dalmatian) toward the end of Wednesday so I'd rather not be on the hook for the emails | 13:24 |
| elodilles | ACK | 13:24 |
| elodilles | btw, do we want to have a meeting next week on Friday? | 13:24 |
| ttx | Press release is at 10am CT like usual | 13:24 |
| ttx | (that's 17:00 CEST) | 13:25 |
| elodilles | +1 | 13:25 |
| ttx | re: meetign, I think it's good to do a quick postmortem while things are still hot | 13:25 |
| elodilles | +1 | 13:25 |
| elodilles | thanks ttx :) | 13:25 |
| ttx | #topic Review countdown email for week R+0 | 13:26 |
| ttx | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 13:26 |
| elodilles | LGTM | 13:27 |
| ttx | ok will sent shortly after | 13:27 |
| ttx | #topic Open Discussion | 13:27 |
| ttx | AFAICT the only remaining flag for the release is what to do with kurur-kubernetes | 13:28 |
| fungi | we'll also need the temporary semaphore removal/revert changes, i can propose those unless someone else is already working on them (should that have been in the r+0 week tasks?) | 13:28 |
| ttx | The discussion is happening on https://review.opendev.org/c/openstack/releases/+/930554 , which is the patch straightening out the various kuryr deliverables | 13:28 |
| ttx | fungi: yes please | 13:29 |
| ttx | kuryr-kubernetes gate is borked and nobody is working on that, but it's still used as a testing dependency for Tacker | 13:30 |
| ttx | so stable/2024.2 testign of Tacker might fail if there is not kuryr-kubernetes stable/2024.2 branch | 13:30 |
| ttx | If that is the case we can always manually create a 2024.2 branch for kuryr-kubernetes, outside of the deliverable file | 13:31 |
| frickler | and never get that cleaned up again, no good idea IMO | 13:31 |
| ttx | so I think we should do that if Tacker testing ends up broken | 13:31 |
| ttx | frickler: what do you mean, never get that cleaned up again? | 13:32 |
| fungi | tacker could just drop the affected tests on stable | 13:32 |
| elodilles | i also added a comment: other option is to cut the branch from 'location' rather than from 'version' (like devstack and requirements branch case). and add a comment to the file why we don't have a release | 13:32 |
| frickler | if it is not in the release file, there will be no transition to unmaintained, no eol | 13:32 |
| frickler | s/release/deliverable/ | 13:33 |
| elodilles | though i'm not 100% sure that our tooling will like that ^^^ | 13:33 |
| ttx | ah, hm | 13:33 |
| fungi | tacker could also switch stable branch tests to use a tagged version of kuryr-kubernetes if they don't want to drop the affected tests | 13:33 |
| ttx | yeah, I feel like those questions are orthogonal to the release. We will not release kuryr-kubernetes for dalmatian, that's the only decision we need to make right now | 13:34 |
| ttx | then Tacker has multiple ways to work around potentially-failing stable branch testing? | 13:35 |
| frickler | +1 | 13:35 |
| ttx | But yes I agree in an ideal scenario we would not create anythign 2024.2 for kuryr-kubernetes | 13:35 |
| ttx | especially not in a deliverables/dalmatian file | 13:36 |
| fungi | if that test dependency is a dead end anyway, they'll need to do something about their choice to depend on it at some point | 13:36 |
| ttx | because that would be very confusing | 13:36 |
| frickler | they could also backport the "do not test with kuryr-kubernetes" fix from master once they finish it | 13:36 |
| ttx | I think they are working on removing it already | 13:36 |
| ttx | ok so I think we should merge https://review.opendev.org/c/openstack/releases/+/930554 asap to finalize the release content | 13:37 |
| frickler | https://review.opendev.org/c/openstack/tacker/+/926504 looks like updated today | 13:37 |
| ttx | otherwise we'll have alarms raised on every script due to unreleased stuff | 13:37 |
| elodilles | :S | 13:38 |
| elodilles | then i'm OK to merge that patch as it is | 13:39 |
| ttx | It's also easy to revert | 13:39 |
| ttx | but I don;t think anyone will convince me it's not the right path | 13:39 |
| frickler | +2 | 13:39 |
| elodilles | +2+W'd | 13:40 |
| ttx | I'll also abandon https://review.opendev.org/c/openstack/releases/+/928531 and https://review.opendev.org/c/openstack/releases/+/929530 | 13:41 |
| elodilles | ++ | 13:41 |
| elodilles | let's abandon them | 13:41 |
| ttx | ok done | 13:42 |
| ttx | Dalmatian review board will soon be clean! | 13:42 |
| ttx | anything else we need to cover? | 13:42 |
| ttx | frickler: have a good time off! | 13:42 |
| * frickler just notes being on holiday for 3 weeks after today. also added to the etherpad, please carry over to the next cycle | 13:42 | |
| frickler | thx | 13:43 |
| fungi | what time on wednesday are people planning to start mashing buttons? i'll set an alarm so i can be awake in case there are issues | 13:43 |
| elodilles | frickler: yepp have a nice relaxing holiday o/ | 13:43 |
| ttx | "On release day (around 10:00 UTC), approve the final release patch created earlier." | 13:44 |
| fungi | and that's based on prior adjustments we made to start earlier due to publication delays and increased test turnaround time we hit in recent releases, right? | 13:45 |
| fungi | i guess that gives us 5 hours to press release | 13:45 |
| fungi | so should suffice | 13:46 |
| ttx | I think so yes | 13:46 |
| elodilles | yepp | 13:46 |
| ttx | Anything else before we close? | 13:46 |
| elodilles | - | 13:47 |
| opendevreview | Merged openstack/releases master: Do not release Kuryr in Dalmatian https://review.opendev.org/c/openstack/releases/+/930554 | 13:47 |
| * fungi has nothing | 13:47 | |
| ttx | woohoo! | 13:47 |
| ttx | #endmeeting | 13:47 |
| opendevmeet | Meeting ended Fri Sep 27 13:47:37 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:47 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-09-27-13.00.html | 13:47 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-09-27-13.00.txt | 13:47 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-09-27-13.00.log.html | 13:47 |
| ttx | Thanks everyone! | 13:47 |
| elodilles | ~o~ | 13:47 |
| elodilles | thanks ttx o/ | 13:47 |
| ttx | elodilles: ping us when the Manila patch is in so taht we review it today | 13:48 |
| elodilles | ttx: ACK | 13:48 |
| opendevreview | Elod Illes proposed openstack/releases master: Release manila RC2 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/930704 | 13:57 |
| elodilles | ttx: ^^^ | 13:57 |
| elodilles | note that storlets also has a merged but unreleased patch on stable/2024.2, but that does not contain any functional change, only devstack plugin change ( https://review.opendev.org/c/openstack/storlets/+/929335 ) so i considered that we don't need an rc2 from that | 14:00 |
| elodilles | and maybe we need another rc2 that i missed when i ran through first at the list of merged & unreleased changes, and that is skyline-console with https://review.opendev.org/c/openstack/skyline-console/+/930399 | 14:02 |
| elodilles | release-team: ^^^ | 14:02 |
| ttx | looking | 14:03 |
| ttx | yeah that looks safe enough | 14:03 |
| ttx | let's rc2 it | 14:03 |
| elodilles | +1 | 14:04 |
| * elodilles is about to create RC2 for skyline-console | 14:04 | |
| opendevreview | Elod Illes proposed openstack/releases master: Release skyline-console RC2 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/930705 | 14:08 |
| elodilles | (the .gitreview and the u-c update patch is not yet merged in skyline-console :'( | 14:08 |
| frickler | elodilles: two more small issues found on https://review.opendev.org/c/openstack/openstack-manuals/+/930331 | 14:09 |
| elodilles | frickler: thanks for checking, will update soon o/ | 14:10 |
| opendevreview | Merged openstack/releases master: Release manila RC2 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/930704 | 14:58 |
| frickler | elodilles: ttx: so we do the skyline rc2 without team feedback? I assume they're long off for the weekend already | 15:15 |
| fungi | remote: https://review.opendev.org/c/openstack/project-config/+/930709 Temporarily remove release docs semaphores [WIP] [NEW] | 15:22 |
| fungi | remote: https://review.opendev.org/c/openstack/project-config/+/930710 Revert "Temporarily remove release docs semaphores" [WIP] [NEW] | 15:22 |
| fungi | i'm setting myself a reminder to un-wip and approve 930709 on tuesday and then 930710 on wednesday once all the release jobs complete | 15:23 |
| elodilles | frickler: good question. maybe we can wait until Monday? | 16:17 |
| ttx | on it | 16:19 |
| ttx | +2, I'll let someone else +A it | 16:21 |
| ttx | elodilles: I overrode the PTL+1 | 16:21 |
| ttx | I prefer to have all RCs clean over the weekend | 16:21 |
| ttx | and a patch up to promote them all to final | 16:22 |
| ttx | and keep release week respins only for release-critical bugs | 16:22 |
| ttx | (i.e. not the Turkish translation) | 16:22 |
| ttx | Approving now since everyone seems to be gone already :) | 16:39 |
| opendevreview | Merged openstack/releases master: Release skyline-console RC2 for 2024.2 Dalmatian https://review.opendev.org/c/openstack/releases/+/930705 | 16:48 |
| opendevreview | Elod Illes proposed openstack/releases master: 2024.2 Dalmatian final releases for cycle-with-rc projects https://review.opendev.org/c/openstack/releases/+/930752 | 16:51 |
| elodilles | and there is the Dalmatian final release patch ^^^ | 16:51 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!