*** bauzas_ is now known as bauzas | 06:56 | |
*** bauzas_ is now known as bauzas | 10:32 | |
elodilles | reminder: weekly meeting will start in less than 30 mins | 12:33 |
---|---|---|
frickler | I'm around, just might be some mins late | 12:53 |
elodilles | #startmeeting releaseteam | 13:00 |
opendevmeet | Meeting started Fri Aug 16 13:00:32 2024 UTC and is due to finish in 60 minutes. The chair is elodilles. 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 |
elodilles | Ping list: release-team elod | 13:00 |
elodilles | #link https://etherpad.opendev.org/p/dalmatian-relmgt-tracking | 13:01 |
elodilles | we are around line 289 | 13:01 |
elodilles | o/ | 13:02 |
elodilles | and let's just wait a bit, maybe folks will join :) | 13:02 |
elodilles | (thanks frickler for the heads up :)) | 13:02 |
elodilles | time is ticking, so let's start, people can read the logs anyway | 13:07 |
elodilles | #topic Review task completion | 13:08 |
frickler | o/ | 13:08 |
frickler | sorry for the delay | 13:08 |
elodilles | o/ | 13:08 |
elodilles | no problem :) | 13:08 |
elodilles | 1st task was: 'Oslo library freeze (elod)' | 13:08 |
elodilles | the countdown mail contained a section about this, | 13:09 |
elodilles | and i've had a chat with damani , one of Oslo's release liaison, | 13:10 |
elodilles | and he also sent out a reminder about this: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/5O4YTNIYJVMLV54UZSNH4MQ7BLKPXHG6/ | 13:10 |
elodilles | 2nd task was: Notify the Infrastructure team to generate an artifact signing key (but not replace the current one yet), and begin the attestation process (ttx) | 13:11 |
fungi | yeah, i'll hopefully get to that in the next week | 13:11 |
elodilles | according to notes: fungi acked the request | 13:11 |
fungi | indeed | 13:11 |
elodilles | fungi: ACK-ACK :) | 13:11 |
elodilles | thanks in advance o/ | 13:12 |
fungi | of course | 13:12 |
elodilles | 3rd task was: | 13:12 |
elodilles | 'Check with the Technical Committee (ttx)' | 13:12 |
elodilles | * to make sure Python runtimes have been determined for the next development cycle https://review.opendev.org/c/openstack/governance/+/926150 | 13:12 |
elodilles | so there is the patch ^^^ | 13:12 |
elodilles | * Zuul job templates have been created to include those runtimes https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926153 | 13:13 |
elodilles | ditto ^^^ | 13:13 |
elodilles | so this is also on track | 13:13 |
elodilles | 4th task: 'Propose DNM changes on repositories where no patches merged recently to check that tests are still passing with the current set of dependencies (libraries, client libraries). (elod)' | 13:13 |
elodilles | patches proposed: https://review.opendev.org/q/topic:release-health-check-cwi-dalmatian | 13:14 |
elodilles | only cought 4 broken gates \o/ | 13:14 |
elodilles | i'll ping the teams to look at the failures | 13:14 |
elodilles | (might be some of the gate failures are just temporary issues, we'll see) | 13:15 |
frickler | might also be worth looking at py312 failures | 13:15 |
frickler | just to be prepared for the next cycle | 13:15 |
elodilles | frickler: i saw that there are more py312 failures, but those are non-voting so far | 13:16 |
elodilles | and i hope that teams are aware of that :) | 13:16 |
frickler | I really wouldn't count on that for most teams, but yeah, not really a release team issue | 13:16 |
elodilles | i saw py312 related patches in multiple projects, so hopefully teams are mostly on track with that | 13:17 |
elodilles | but yepp, a couple of weeks, and py312 jobs will be voting on master branch | 13:17 |
elodilles | and that's all about the 'Review task completion' topic | 13:18 |
elodilles | next one: | 13:18 |
elodilles | #topic Assign R-6 week tasks | 13:18 |
elodilles | there's only one task | 13:19 |
elodilles | note that i'll be off on Mon-Tue | 13:19 |
elodilles | so i can take the task, but can only propose patches by Wednesday | 13:19 |
frickler | is there some tool for that task? | 13:19 |
frickler | I could take a look then, but maybe also not earlier then Wednesday | 13:20 |
elodilles | tools/process_auto_releases.sh | 13:20 |
elodilles | this is the script ^^^ | 13:20 |
frickler | o.k., I'll take a look and bug you if I can't make progress | 13:21 |
elodilles | frickler: and here is the task description in the Release process: https://releases.openstack.org/reference/process.html#r-6-week-final-library-release-deadline | 13:21 |
elodilles | frickler: thanks in advance o/ | 13:22 |
elodilles | if you are unsure in something, then we can look at the task on Wednesday | 13:22 |
frickler | ty | 13:23 |
elodilles | move on then! | 13:23 |
elodilles | #topic Review countdown email for week R-6 | 13:24 |
elodilles | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 13:24 |
elodilles | please review ^^^ | 13:24 |
elodilles | i'll send it later on today if it looks fine for you | 13:25 |
frickler | long one, but lgtm | 13:26 |
elodilles | yepp. we are closer and closer to final release, so there will be more things to take care by PTLs & teams o:) | 13:27 |
elodilles | thanks then! | 13:27 |
elodilles | #topic Open Discussion | 13:27 |
elodilles | anything to discuss? | 13:27 |
frickler | I have a patch open to update the update-constraints job https://review.opendev.org/c/openstack/project-config/+/926405 | 13:27 |
* elodilles clicks | 13:27 | |
frickler | since it is difficult to test this ahead of time, it will need some care with the next release after it is merged | 13:28 |
frickler | the most risky part is switching from focal to noble I think | 13:28 |
elodilles | yepp, that's quite a jump :X | 13:29 |
elodilles | otherwise it sounds like a plan | 13:29 |
frickler | yes, but I didn't think that going to jammy would be much less risky, and this way we can skip one jump | 13:29 |
elodilles | +1 | 13:30 |
elodilles | when do you plan to merge and check? | 13:30 |
frickler | so I guess I'll W-1 this until wednesday, so that we can make a release in time after merging it | 13:30 |
elodilles | frickler: sounds good to me! | 13:31 |
frickler | because doing this now before the weekend doesn't sound useful | 13:31 |
elodilles | yepp, not a typical 'before weekend' task :] | 13:31 |
frickler | and that's already all I had | 13:32 |
elodilles | mostly the py312 (default in noble) could cause issues, i guess | 13:32 |
elodilles | but fingers crossed | 13:32 |
elodilles | we can do test release with 'release-test' deliverable | 13:33 |
frickler | it should be easy to create the reqs patch manually if it fails and then fix the job or worst case revert | 13:33 |
elodilles | true | 13:33 |
frickler | release-test isn't in u-c, or is it? | 13:33 |
elodilles | hmmm, you are right, i think it isn't | 13:34 |
elodilles | anyway, as you said, should be easy to handle the fail case | 13:34 |
elodilles | OK, if no more topics, | 13:34 |
elodilles | then let's close the meeting! | 13:35 |
elodilles | thanks for participating o/ | 13:35 |
frickler | \o | 13:35 |
elodilles | #endmeeting | 13:35 |
opendevmeet | Meeting ended Fri Aug 16 13:35:22 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:35 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-08-16-13.00.html | 13:35 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-08-16-13.00.txt | 13:35 |
opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-08-16-13.00.log.html | 13:35 |
opendevreview | Merged openstack/releases master: hacking 7.0.0 https://review.opendev.org/c/openstack/releases/+/926053 | 16:01 |
*** bauzas_ is now known as bauzas | 18:55 | |
*** bauzas_ is now known as bauzas | 20:12 | |
*** bauzas_ is now known as bauzas | 22:04 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!