Friday, 2021-11-19

*** ysandeep|out is now known as ysandeep05:14
*** brinzhang_ is now known as brinzhang07:44
*** akekane_ is now known as abhishekk07:52
*** amoralej|off is now known as amoralej08:10
opendevreviewMichal Nasiadka proposed openstack/releases master: Release Yoga RC3 for Kolla and Kolla-Ansible  https://review.opendev.org/c/openstack/releases/+/81835308:38
*** ysandeep is now known as ysandeep|afk11:04
opendevreviewRiccardo Pittau proposed openstack/releases master: Release ironic-lib 5.0.1 for xena  https://review.opendev.org/c/openstack/releases/+/81853811:47
opendevreviewRiccardo Pittau proposed openstack/releases master: Release ironic-lib 4.6.3 for wallaby  https://review.opendev.org/c/openstack/releases/+/81853911:48
*** ysandeep|afk is now known as ysandeep12:22
*** amoralej is now known as amoralej|lunch13:24
opendevreviewMerged openstack/releases master: Release Yoga RC3 for Kolla and Kolla-Ansible  https://review.opendev.org/c/openstack/releases/+/81835313:49
elodillesreminder: meeting in a couple of mins13:54
elodilles(Shouldn't that be Xena RC3? ^^^)13:54
elodillesok, let's start14:01
elodilles#startmeeting releaseteam14:01
opendevmeetMeeting started Fri Nov 19 14:01:14 2021 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'releaseteam'14:01
ttxo/14:01
hberaudo/14:01
elodilleshi o/14:01
elodilles#link https://etherpad.opendev.org/p/yoga-relmgt-tracking14:01
elodilleswe are at line 7314:01
elodilleslet's start with the 1st topic14:02
elodilles#topic Review task completion14:02
elodilles#info Ensure that all trailing projects have been branched for the previous series14:02
elodillesthat was on me14:02
elodillesI've proposed the patches, I hope i did it right14:03
elodilles#link https://review.opendev.org/q/topic:trailing-xena14:03
elodillesthese are the patches ^^^14:03
ttxIIRC our deadline is pretty fuzzy on those, at least the patches will start the discussion14:04
hberaud+114:04
elodillesyes, the trailing delivery deadline is December 16th14:04
elodillesso we are one month ahead of that14:05
elodillesok, if nothing else for this then i'll continue with the next task14:05
elodilles#info Propose autoreleases for cycle-with-intermediary libraries which did not release since the previous release14:06
elodillesi've generated the patches a bit late for this, instead of beginning of week, i created those yesterday afternoon14:07
elodilles#link https://review.opendev.org/q/topic:yoga-milestone-114:07
ttxok so we might give them a bit more time before force-approving those without -114:08
ttx(in theory we would have done that now)14:08
ttx(and give those with -1 a few extra days)14:08
elodillesnote: there were quite many that were listed as not released yet, but either didn't have any change at all or just CI/tests/branch setup releated patches were merged14:08
ttxyeah those can be ignored14:08
hberaudthe automaton patch can be abandonned14:09
hberaudI left a comment14:09
elodillesttx: yes, thanks, let's give some time until the force-approve14:09
hberaudhttps://review.opendev.org/c/openstack/releases/+/81840314:09
elodilleshberaud: looking14:09
elodilleshberaud: thanks, abandoned!14:11
hberaudty14:11
elodillesdo we want to agree on a force-approval deadline, like Tuesday, or something?14:12
ttxI'd say approve all without -1s by Tuesday, then finalize those with -1s by end of week14:13
hberaudWednesday, seems more appropriate14:13
hberaudor the end of week14:13
ttxI don;t want to delay too much14:13
ttxbasically push by two business days14:14
hberaudwfm14:14
elodillesok14:14
elodilles#agreed yoga-milestone-1 patches: approve all without -1s by Tuesday, then finalize those with -1s by end of week14:15
*** amoralej|lunch is now known as amoralej14:15
elodillesok, next topic14:15
elodilles#info To catch if there are acl issues in newly created repositories14:15
elodillesttx: this was yours14:15
ttxyep, the script revealed one gap14:16
ttxhttps://review.opendev.org/c/openstack/project-config/+/818356 (tap-as-a-service)14:16
ttx(basically the idea is to make sure releases go through openstack/releases, so remove direct tagging rights14:16
ttx)14:17
ttxnothing more to say14:17
elodilles#link https://review.opendev.org/c/openstack/project-config/+/81835614:17
elodillesttx: cool, thanks!14:17
elodillesfor the explanation, too14:17
elodillesok. the countdown email is not yet ready, as I'll send it after the meeting and when we are there :)14:18
elodillesso next topic14:18
fungion a related note, was there ever a formal conclusion as to whether the release team can handle sigs' repos?14:18
elodilles#topic Assign R-18 tasks14:18
elodillesfungi: i don't know. hberaud , ttx , do you remember such?14:20
hberaudnope14:20
ttxWe only do openstack release14:20
ttxi.e. deliverables from project teams14:20
ttxthat's they key difference between project teams and sigs14:21
hberaudAgreed with ttx 14:21
ttxso we tend to explictly stay away from SIG repos14:21
fungiokay, i recall it came up on the ml last week, i thought it was ansible-collections-openstack but might have been somthing else14:21
ttxthat's why QA is still a project team14:21
ttx(and with release management the onlt horizontal team left)14:22
ttxit's because their repos are handled by us as part of "the release"14:22
fungioh, i see where i got confused14:23
ttx(+ requirements)14:23
fungielodilles posted on openstack-discuss about a release job failure for ansible-collections-openstack but that was one they tagged themselves i guess14:23
ttx(I tried to clean things up over the years and I think we finally got there)14:23
ttxyes release jobs failure can be triggered by openstack/releases or direct tags :)14:24
elodillesyes, and since it was not familiar to me i rather forwarded it to ML o:)14:25
fungiyeah, he mis-attributed it to the ansible team in the e-mail, but that was it14:25
fungii thought maybe it was one which had been handled via openstack/releases but looks like it wasn't14:25
fungiconfusion cleared, thanks14:25
ttxthe only way to be sure bnothing falls into the cracks is really to have a finite, defined list of things we handle14:26
ttxotherwise you're just never sure14:26
fungiyes, i agree14:26
elodillesyepp, that's for sure14:26
ttxit's been tricky enough to compile that list (see release-management key in projects.yaml)14:26
ttxthere were exceptions all over the map :)14:27
ttxbut we are pretty good now... just need to periodically check all data is aligned14:27
ttxlike that ACL check we did this week14:27
fungimakes sense, that's what reminded me14:27
elodillesok, so, next topic: assigning R-18 tasks14:28
elodillesthere is only 1 task14:29
elodillesi guess this could be "all", right? o:)14:29
hberaudyes14:29
elodilles"Review any remaining milestone-1 exceptions"14:29
elodillesadded "all" to that then. thanks14:30
elodillesnext topic:14:30
elodilles#topic Review countdown email contents14:30
elodilles#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:30
elodillesi've added and edited the mail ^^^14:31
elodillesthere is one thing: we don't have release cycle goal (page)14:31
ttxIt's hard to say we are past Yoga-114:32
elodillesso I'll remove that if you confirm that is OK14:32
ttxI'd wait until next week to send this one14:32
ttxLike wait until we process things on tuesday14:32
elodillesttx: hmm, yes, since the shifted deadline to Tuesday14:32
elodillesttx: that works for me14:33
hberaudWFM14:33
ttxotherwise looks good!14:33
elodillesok, thanks14:33
hberaud+114:33
elodilles#action to elod: Send countdown mail on Tuesday, after Yoga-1 milestone patches have been merged14:34
elodilles(hope i remember correctly for the keywords :))14:34
elodillesanyway14:34
elodillesnext topic then14:34
elodilles#topic     Branches without releases https://review.opendev.org/c/openstack/releases/+/81844514:35
ttxyeah I was wondering about that one14:35
ttxI think we only branch on release points, on purpose14:36
elodillesopenstack-ansible-roles have similar branching, i mean, without any release,14:37
elodillesjust the hashes, set as location14:37
ttxthe error looks more like a bug than a validation rule failure14:37
ttx    latest_release = deliv.releases[-1]14:37
ttxIndexError: list index out of range14:37
hberaudthe openstack-ansible-role is tagless14:38
hberaudhttps://opendev.org/openstack/releases/src/branch/master/deliverables/wallaby/openstack-ansible-roles.yaml#L314:38
elodilleshberaud: you are right14:38
hberaudthe tripleo-docs is a cwi deliverable14:38
hberaudthis is why it complain with it14:38
hberaudI don't think this is possible to branch without releasing something14:39
hberaud(in the tripleo-docs context)14:40
ttxat the very minimum we should catch that case because currently the script just errors out14:40
hberaudindeed14:40
ttxbut yes, the error matches14:40
ttx"stable branches must be created from the latest tagged release..."14:41
ttxhere the script errors out trying to grab the latest release14:41
ttxbut there is none14:41
ttxIf it was tagless it would pass14:42
hberaudyes14:42
ttxor "upstream"14:42
elodilleson the other hand do we want to allow this late branch cutting (for wallaby, in this case)?14:42
hberaudit can't hurt14:42
elodillesok14:42
ttxok, who replies?14:43
hberaudthis is a trailing deliverable14:43
hberaudthis is why we missed to branch it14:43
elodillesi see14:43
hberaudit went under our radar14:44
elodillesok, so I can comment on the patch that this requires a release as well. <- is this OK?14:45
ttxwfm14:45
hberaudwfm14:46
elodillesgood. and another thing is the validation, it could be fixed with some clear error message then, i guess14:47
elodillesi'll try to look into it. of course, if someone has an idea for how to fix, then please propose a patch for that :)14:49
elodillesok, next topic14:49
elodilles#topic Proposing skipping meeting next week (just need to make sure we process all yoga-1)14:49
ttxI won;t be around anyway, but there is also no task the week after14:50
hberaudwfm14:50
ttxtrick is we still need to doublecheck that all yoga-1 is handled14:50
elodillesyes, I mean, now we'll have the yoga-milestone-1 patches, but that can be handled without the meeting :)14:51
ttx++14:52
elodillesok14:52
elodillesi've added a note to meeting agenda after (skip + make sure everything is good with yoga-milestone-1)14:54
elodilless/after//14:54
elodilleslast topic:14:54
elodilles#topic Open Discussion14:54
elodillesanything to mention? anyone?14:55
ttxnope14:55
funginothing here14:56
elodillesokay, then thanks everyone, let's close the meeting14:57
elodilles#endmeeting14:57
opendevmeetMeeting ended Fri Nov 19 14:57:22 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2021/releaseteam.2021-11-19-14.01.html14:57
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2021/releaseteam.2021-11-19-14.01.txt14:57
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2021/releaseteam.2021-11-19-14.01.log.html14:57
hberaudnope14:57
hberaudelodilles: thanks14:57
elodillesthanks, too o/14:57
*** ysandeep is now known as ysandeep|out15:13
opendevreviewHervĂ© Beraud proposed openstack/releases master: Fix validation when tags are missing and a branch is requested  https://review.opendev.org/c/openstack/releases/+/81856215:17
hberaudttx, elodilles: here is a fix ^ to handle the problem with https://review.opendev.org/c/openstack/releases/+/81844515:18
elodilleshberaud: thanks \o/ will review shortly15:19
hberaudI just have some concern concerning about where we need to handle the 'ValueError'15:20
opendevreviewHervĂ© Beraud proposed openstack/releases master: Fix validation when tags are missing and a branch is requested  https://review.opendev.org/c/openstack/releases/+/81856215:30
opendevreviewElod Illes proposed openstack/releases master: [manila] Transition Ussuri to EM  https://review.opendev.org/c/openstack/releases/+/81759916:12
opendevreviewMerged openstack/releases master: [nova] Transition Ussuri to EM  https://review.opendev.org/c/openstack/releases/+/81760616:16
*** marios is now known as marios|out16:47
clarkbHello release team. The latest PBR release 5.8.0 should make it possible for PBR users to use modern python packaging tooling specifications via pyproject.toml16:55
clarkbhttps://review.opendev.org/c/opendev/bindep/+/816741 was my test change and we found some issues there with 5.7.0 though those issues only arise if you try to do non backward compatible usage without setup_requires16:55
clarkbI don't know what the correct choices for openstack packaging will, but wanted to mention that this seems viable now should you want to go that route. One thing worth noting is that you can specify the version of setuptools you want if you use this tooling. Doing this has come up in the past as somethign that might be desireable16:56
*** amoralej is now known as amoralej|off17:29
*** whoami-rajat__ is now known as whoami-rajat17:42
elodillesclarkb: thanks for the info! i am not fully familiar with this pyproject.toml yet, but the setuptools pinning looks good :)19:06
clarkbelodilles: note I would still use it sparingly as I'm not sure how it would interfere with things like distro packaging if setuptools is outside the expected range. But at least it becomes a possibility19:07
elodilleshmmm, i see, good point19:09

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