Friday, 2022-02-18

*** dviroel|out is now known as dviroel10:54
elodillesreminder: weekly meeting will start in 22 mins :]13:38
elodillesshowtime!14:00
elodilles#startmeeting releaseteam14:00
opendevmeetMeeting started Fri Feb 18 14:00:26 2022 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'releaseteam'14:00
elodillesPing list: hberaud ttx armstrong damani 14:00
armstrongo/14:00
elodilles#link https://etherpad.opendev.org/p/yoga-relmgt-tracking14:00
elodilleso/14:01
elodilleswe are at line 27014:01
elodilleshmm. we have a bit less number of participants so far, that i've expected14:05
fungii'm around, just very quiet14:05
elodillesfungi: o/14:05
elodillesok, let's start14:05
elodilles#topic Review task completion14:06
elodilles1st task: "Check with the Technical Committee to make sure Python runtimes have been determined for the next development cycle and that Zuul job templates have been created to include those runtimes."14:06
elodillesit was on hberaud and damani 14:06
elodillesso I'll check with them later14:07
fungii haven't seen any changes proposed for zen python runtimes14:07
elodillesyou mean Zed :)14:07
elodillesbut yes :)14:07
fungizero14:07
elodilles:]14:07
fungiand yoga is definitely the last listed on the pti page14:07
elodillesanyway, i'll add it to next week tasks again14:08
elodillesjust to not forget about this14:09
elodillesnext task:14:09
elodilles"Follow-up task: Make sure the next development series name has been added to the data/series_status.yaml file (elod)"14:09
elodillesi've added to the proposed schedule patch: https://review.opendev.org/c/openstack/releases/+/824489/5/14:10
elodillesi wanted to ask whether we can merge this, but let's wait with this question till next week14:10
elodilles#action Review and merge if possible: https://review.opendev.org/c/openstack/releases/+/824489/5/14:11
elodillesnext task then:14:11
elodilles"Propose autoreleases for cycle-with-intermediary libraries (excluding client libraries) which had commits that have not been included in a release. (damani, elod)"14:11
elodilleswe did that with damani, patches are here: https://review.opendev.org/q/topic:yoga-final-non-client-libs14:12
elodillesmost of the patches have been merged,14:12
elodillesthere are some -1's,14:13
elodillesand some open patches without responses14:13
elodillessince deadline is today, i'll merge them after the meeting14:13
elodillesexcept the ones with -114:14
armstrongwhat about those without PTL approve?14:14
elodillesarmstrong: we need to force merge them14:15
elodillesas it is stated in the commit message14:15
armstrongok14:16
elodilleswe are done with this weeks tasks14:16
elodilles#topic Assign R-5 week tasks14:16
elodillesI'll add my name to the tasks, but feel free to add yours as well if you can do some of them14:19
armstrongok14:20
elodillesthanks, let's move on14:21
armstrongI will add my name beside yours 14:21
elodillesarmstrong: ++14:21
elodilles#topic Review countdown email contents14:21
elodilles#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:22
elodillesplease review, and let me know if you've found any mistake ^^^14:22
armstrongthe email LGTM!14:29
elodillesthanks armstrong o/14:29
elodilles:)14:29
elodilleslet's go to the next topic then14:29
elodilles#topic Removing TC tags framework14:29
elodilles#link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/thread.html#2721414:29
armstrongso we just have one week from the  RC deadline to final release?14:30
elodillesarmstrong: exactly. 1 week only.14:30
elodillesi mean14:30
armstrongok thanks elodilles 14:31
elodillesRC1 deadline: March 10th, 202214:31
elodillesFinal RC deadline: March 24th, 202214:31
elodillesthen 1 week: Final Yoga release:  March 30th, 202214:31
fungiyeah, there's more than one "rc deadline" so don't get confused14:31
elodillesyepp14:32
elodillesso, about the topic:14:32
fungithe rc1 deadline is the date by which projects need an rc1 tag, the final rc deadline is the last date projects are allowed to request subsequent rc tags after rc114:32
elodillesif they need another. yes. :)14:33
elodillesso, about the tag removal: as the linked mail shows TC decided to get rid of the repo tags14:34
elodilleslike stable:follows-policy, and others14:35
elodillesin our code we use ^^^ tag (to show some banner)14:35
elodillesttx said and I wrote too (to the mailing list) that we can drop this14:36
elodillesI've propesed a small patch already (but got the comment that we need further cleanups as repo.tags are used other places as well)14:37
elodillesI don't see any problem with that, but wanted to double check with the team, whether anyone sees any problem we could face by removing the tags14:38
elodilleshberaud ttx : ping me if something comes to your mind that could be problem for us with this ^^^14:39
elodillesi'll update the proposed patch, or rather create a follow up patch, and we will see14:40
elodillesi think that it about this topic14:41
fungii'm doing similar removal work for the vulnerability:managed tag, and will be following up with the foundation webdev folks about any changes needed to the software lists on the www site14:41
fungiright now some of those governance tags result in specific things being included in the project list14:41
elodillesto tell you the truth i don't know all the tags and where they are used. I've seen that project pages there are things triggered by the tags, but that's all :)14:44
elodilles#topic Open Discussion14:45
elodillesanything to mention here?14:45
fungii've got the zed cycle artifact signing key generated, should have a change pushed shortly to record what it will be14:46
fungibut obviously we won't put it into use by the jobs until after yoga is done14:47
elodillesfungi: thanks for the info!14:47
fungithis is just to get the attestation process for the new key bootstrapped14:47
elodillesanything regarding that, that we could help with?14:47
fungireviewing the change once it's up, sure14:49
fungithat'll be the next step anyway14:49
elodillesjust add me as reviewer and I'll review it! :) thanks!14:49
fungiyou bet14:49
elodilles:]14:50
elodillesany other topic?14:50
funginothing from me14:51
armstrongnothing from me14:51
elodillesOK, thanks, then lets finish the meeting!14:51
fungithanks elodilles!14:51
elodillesthanks fungi and armstrong for joining! o/14:51
armstrongthanks14:51
elodilles#endmeeting14:52
opendevmeetMeeting ended Fri Feb 18 14:52:08 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2022/releaseteam.2022-02-18-14.00.html14:52
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2022/releaseteam.2022-02-18-14.00.txt14:52
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2022/releaseteam.2022-02-18-14.00.log.html14:52
armstrongI will ping you later on the tasks14:52
elodillesarmstrong: cool, just ping me here14:52
elodillesarmstrong: i'll also ping you if i start any of those tasks14:53
armstrongok14:53
dviroelelodilles: hi o/ 14:54
elodillesdviroel: hi14:54
dviroelelodilles: we need a new release of oslo-rootwrap - to get a new bugfix merged14:55
dviroelelodilles: https://github.com/openstack/oslo.rootwrap/commits/master14:55
dviroelelodilles: how should I proceed? just propose the patch?14:55
elodilleswas final oslo.rootwrap already released for yoga?14:56
elodillesdviroel: ok, now i've checked, it's an independent deliverable14:58
elodillesdviroel: just propose please a release patch, and the team will review it14:58
dviroelelodilles: ah ok, thanks - doing it now14:59
elodillesdviroel: no worries14:59
elodillesdviroel: i'll review it when it's there15:00
opendevreviewDouglas Viroel proposed openstack/releases master: New bugfix release of oslo-rootwrap  https://review.opendev.org/c/openstack/releases/+/82990215:03
opendevreviewMerged openstack/releases master: Release final metalsmith for Yoga  https://review.opendev.org/c/openstack/releases/+/82907515:25
opendevreviewMerged openstack/releases master: Release final os-brick for Yoga  https://review.opendev.org/c/openstack/releases/+/82908215:26
opendevreviewMerged openstack/releases master: Release final blazar-nova for Yoga  https://review.opendev.org/c/openstack/releases/+/82906915:26
opendevreviewMerged openstack/releases master: Release final os-vif for Yoga  https://review.opendev.org/c/openstack/releases/+/82908415:29
opendevreviewMerged openstack/releases master: Release final cliff for Yoga  https://review.opendev.org/c/openstack/releases/+/82907215:36
opendevreviewMerged openstack/releases master: Release final osc-lib for Yoga  https://review.opendev.org/c/openstack/releases/+/82908615:36
opendevreviewMerged openstack/releases master: Release final heat-translator for Yoga  https://review.opendev.org/c/openstack/releases/+/82956915:39
opendevreviewMerged openstack/releases master: Release final monasca-statsd for Yoga  https://review.opendev.org/c/openstack/releases/+/82907715:43
opendevreviewMerged openstack/releases master: Release final mistral-lib for Yoga  https://review.opendev.org/c/openstack/releases/+/82957015:45
opendevreviewMerged openstack/releases master: Release final monasca-common for Yoga  https://review.opendev.org/c/openstack/releases/+/82907615:45
opendevreviewJeremy Stanley proposed openstack/releases master: Publish the Zed Cycle signing key for future use  https://review.opendev.org/c/openstack/releases/+/82993315:46
fungielodilles: ^15:46
opendevreviewMerged openstack/releases master: Release final tosca-parser for Yoga  https://review.opendev.org/c/openstack/releases/+/82910315:46
elodillesfungi: thx!15:51
fungimy pleasure15:52
*** dviroel is now known as dviroel|lunch16:29
elodilleshmm, we have a release job failure: publish-openstack-releasenotes-python3 https://zuul.opendev.org/t/openstack/build/89bbee2d80044a35b37fd68c8549db2116:38
elodillesit says: <reno.sphinxext origin/stable/newton>:96:hardcoded link 'https://bugs.launchpad.net/bugs/1558690' could be replaced by an extlink (try using ':lpbug:`1558690`' instead)16:39
elodillesthis is a new sphinx feature (latest sphinx release, 4.4.0 from january 16): 16:43
elodilleshttps://github.com/sphinx-doc/sphinx/pull/980016:43
elodillesi just don't know why it wasn't caught by the docs job at check & gate16:44
opendevreviewDr. Jens Harbott proposed openstack/releases master: Publish the Zed Cycle signing key for future use  https://review.opendev.org/c/openstack/releases/+/82993316:44
*** dviroel|lunch is now known as dviroel17:32
*** dviroel is now known as dviroel|afk20:09
smcginniselodilles: I wonder if there is a way to disable that. I'm sure we have a LOT of full URL links to launchpad bugs out there.21:15
smcginnisDon't really like that sphinx would have a specific tag for a specific bug reporting system either.21:15
smcginnisBut good question why the earlier job didn't catch that. Could look in the earlier job run and see if it somehow used an older sphinx.21:16

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!