Thursday, 2021-03-11

*** tosky has quit IRC00:26
*** openstackgerrit has quit IRC03:25
*** diablo_rojo has quit IRC03:48
*** armstrong has quit IRC04:04
*** e0ne has joined #openstack-release04:12
*** e0ne has quit IRC04:12
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** e0ne has joined #openstack-release06:24
*** e0ne has quit IRC06:24
*** sboyron has joined #openstack-release07:07
*** slaweq has joined #openstack-release07:13
*** eolivare has joined #openstack-release07:34
yoctozeptohello dears, I have a question regarding openstacksdk release; I have just noticed it is not treated as "client library" and had its "final release" on Mar 03; the issue is masakariclient has code that depends on unreleased openstacksdk features; please let me know if openstacksdk may release again for wallaby or masakari is doomed (/me07:35
yoctozeptocross-posting this message on #openstack-release and #openstack-sdks)07:35
*** tosky has joined #openstack-release08:33
yoctozeptospecifically I am about https://review.opendev.org/c/openstack/openstacksdk/+/77729908:49
*** tosky_ has joined #openstack-release08:52
*** tosky is now known as Guest8681408:53
*** tosky_ is now known as tosky08:53
*** Guest86814 has quit IRC08:55
*** openstackgerrit has joined #openstack-release09:11
openstackgerritHervé Beraud proposed openstack/releases master: Adding the date of Xena's PTG  https://review.opendev.org/c/openstack/releases/+/77994409:11
ttxyoctozepto: we can still do bugfix releases09:39
ttxand exceptionally consider feature releases09:39
ttxthe earlier the better :)09:40
hberaudclarkb: o/ If it's really need we could grant an exception and wait until early next week.09:43
yoctozeptottx: like, today with masakariclient?09:44
ttxyoctozepto: yeah09:46
ttxmaybe start a thread on openstack-discuss to document the exception09:47
ttxBut if the added features are specific to masakari I don't think that would impact anyone09:47
ttxAlso it's questionable that openstacksdk should follow the early library deadline, for that precise reason09:48
hberaudWhat's missing? the microversion sync?09:48
ttxwe release python-*client the same time as parent projects so that late features can be taken into account09:48
ttxit seems appropriate that openstacksdk is in the same bucket09:48
hberaudagree09:49
ttxalso more generally, all those safeguards are a lot less needed now that we move slower and break less things09:49
ttxso exceptions can be considered liberally09:49
openstackgerritMerged openstack/releases master: Adding the date of Xena's PTG  https://review.opendev.org/c/openstack/releases/+/77994409:55
yoctozeptottx, hberaud: thanks, I will handle this09:56
hberaudthanks09:56
hberaudyoctozepto: Do you plan to start the ML thread?09:57
yoctozeptohberaud: yes, but later; in a meeting right now; it would be cool if you started it as well09:59
hberaudhm ok... then I'll bring that on the angle of the issue and on the angle of openstackSDK status compared to other clients. I'll ignore the FFE part.10:03
hberaudyoctozepto: ^10:03
hberaudttx: any reason to not +W'd? https://review.opendev.org/c/openstack/releases/+/77920510:05
ttxwas wondering he we should not give a heads-up to the list before W+1ing those10:07
ttxWas there a thread about those yet?10:07
hberaudyoctozepto: well, finally, I'll bring the FFE too10:07
hberaudttx:10:07
hberaudttx: yes10:07
hberaudlemme grab the link10:08
hberaudI opened a related threads few months ago10:08
hberaudttx: http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018527.html10:08
hberaudttx: the thread is only related to the oslo scope10:09
openstackgerritMerged openstack/releases master: Release monasca-grafana-datasource 1.3.0  https://review.opendev.org/c/openstack/releases/+/77945410:09
ttxOK.. I wanted to complete the discussion on pycadf and have us post some sort of conclusion to that thread before pushing the button...10:09
ttxbut feel free to if you;re comfortable with it :)10:09
hberaudDo you want to start the thread?10:09
ttxstill waiting for feedback on that pycadf review10:10
hberaudI'm confortable with oslo10:10
ttxthen we can reply to the old thread saying what we ended up doing10:10
hberaudOk I'll send a last reply to give a last chance to raise hands10:11
hberaud(on my original thread about oslo)10:11
ttxmaybe say ok we are about to move X and Y. For pycadf the jury is still out10:12
hberaudI think pycaf and monasca should be handled separatelly10:12
hberaudI see10:12
hberaudok10:12
hberaudI'll submit a all in one email and put the reference about the previous discussion on oslo10:13
openstackgerritMerged openstack/releases master: Release python-swiftclient 3.9.1 for Ussuri  https://review.opendev.org/c/openstack/releases/+/77843810:14
ttxhberaud: regarding the python clients that did not have any significant change merged during wallaby... we should still do a wallaby release to support the branch, right10:14
hberaudWhat do you suggest?10:15
hberaudTo cut the branch now?10:16
ttxI'm not sure what's the process in that case. The safe bet is to make a release and branch10:16
ttxas we are 100% sure that works10:16
*** dtantsur|afk is now known as dtantsur10:17
hberaudok10:17
ttxunless we have examples of branches being created from previous release tags10:17
openstackgerritMerged openstack/releases master: Cinder team releases for stable/ussuri  https://review.opendev.org/c/openstack/releases/+/77919910:17
openstackgerritMerged openstack/releases master: Release final python-glanceclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77965310:17
ttxwe had a discussion about that at some PTG I remember10:17
ttxtrying to find it10:18
yoctozeptottx, hberaud: what I noticed is that openstacksdk made a "final release" but did not branch10:21
yoctozeptoanother reason for my confusion10:21
hberaudI take note10:21
ttxso on one hand process says "If it is not OK to transition them, create a new stable branch from the latest release from the previous series"10:22
ttxon the other hand... let me see if I can find any example of that ever being attempted10:22
hberaudok10:23
hberaudI'm on the emails stuff for now10:23
hberaudIf you find something useful do not hesitate to update our process10:24
ttxhberaud: yeah, that was never done. We never created a stable branch from a tag in a previous release10:26
ttxi don;t think we should start innovating, tags are cheap10:27
ttxSo I'll post a minor bump and branch for those10:27
ttxand be on the safe side10:27
ttxI'll add a patch to process to be more explicit10:28
*** e0ne has joined #openstack-release10:30
openstackgerritYasufumi Ogawa proposed openstack/releases master: Release final python-tackerclient for Wallaby  https://review.opendev.org/c/openstack/releases/+/77897210:32
openstackgerritThierry Carrez proposed openstack/releases master: Clarify process for libraries without changes  https://review.opendev.org/c/openstack/releases/+/77996510:37
hberaudttx: excellent thanks10:37
hberaudI agree tags are cheap and we don't need to enter in a danger zone now10:38
openstackgerritThierry Carrez proposed openstack/releases master: Release sushy-cli for wallaby  https://review.opendev.org/c/openstack/releases/+/77997010:48
ttxthis tool is fancy10:49
hberaudWhich? autorelease?10:49
ttxyeah10:50
ttx<grumpy_old_man/>back in my time we didn't have fancy tools</>10:50
hberaudlol10:50
hberaudOne good improvement would be to retrieve similar batches from previous cycle10:50
hberaudand to formalize batch naming10:51
openstackgerritThierry Carrez proposed openstack/releases master: Release python-ironic-inspector-client for wallaby  https://review.opendev.org/c/openstack/releases/+/77997110:51
hberaudto get a linear history from one cycle to another10:51
openstackgerritThierry Carrez proposed openstack/releases master: Release blazar-nova for wallaby  https://review.opendev.org/c/openstack/releases/+/77997210:52
hberaudI think that first I'll add this kind of formalization in our process10:52
hberaudand after one cycle we'll be able to retrieve topics easily and so batches too10:52
openstackgerritThierry Carrez proposed openstack/releases master: Release python-aodhclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77997410:53
openstackgerritThierry Carrez proposed openstack/releases master: Release python-barbicanclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77997510:54
hberaudSince we goes more and more in a maintenance mode, I don't expect that our process will disrupt from one day to  another.10:54
hberaudAlso that could allow to generate related metrics10:55
openstackgerritThierry Carrez proposed openstack/releases master: Release python-adjutantclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77997710:55
openstackgerritMerged openstack/releases master: Release final python-senlinclient for Wallaby  https://review.opendev.org/c/openstack/releases/+/77896910:55
openstackgerritMerged openstack/releases master: Add Wallaby release highlights for Octavia  https://review.opendev.org/c/openstack/releases/+/77938110:55
openstackgerritMerged openstack/releases master: Add wallaby release highlights for Designate  https://review.opendev.org/c/openstack/releases/+/77938510:56
openstackgerritThierry Carrez proposed openstack/releases master: Release python-zunclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77997810:56
openstackgerritThierry Carrez proposed openstack/releases master: Release python-zaqarclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77997910:57
openstackgerritMerged openstack/releases master: Release final python-monascaclient for Wallaby  https://review.opendev.org/c/openstack/releases/+/77896610:58
openstackgerritMerged openstack/releases master: Release final python-octaviaclient for Wallaby  https://review.opendev.org/c/openstack/releases/+/77896710:58
openstackgerritThierry Carrez proposed openstack/releases master: Release python-watcherclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77998011:01
openstackgerritThierry Carrez proposed openstack/releases master: Release python-solumclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77998111:01
openstackgerritThierry Carrez proposed openstack/releases master: Release ceilometermiddleware for wallaby  https://review.opendev.org/c/openstack/releases/+/77998211:02
*** e0ne has quit IRC11:03
openstackgerritMaysa de Macedo Souza proposed openstack/releases master: Add Kuryr Wallaby highlights  https://review.opendev.org/c/openstack/releases/+/77984811:07
ttxhberaud: I analyzed the recent job failure, weird yarn error11:39
ttxposted to the ML for further discussion11:39
hberaudack11:49
hberaudI didn't see the error yet11:49
hberaudyoctozepto, ttx: The FFE and the debate about library vs client-library for openstacksdk => http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021004.html12:19
hberaudttx: What's about library with no tags?12:27
hberaudoslo by example12:27
hberaudthis is the same use case12:27
hberaudIIRC I ignored those without significant changes12:27
hberaudlemme check first12:32
hberaudok... if I'm right only 4 oslo projects are missing12:34
hberaudnot 4 but 3 => oslo.(limit|middleware|privsep)12:34
ttxok probably won't have time to generate those today12:36
hberaudall the rest seems either shifting to independent or already proposed but not yet merged (release patches (https://review.opendev.org/q/topic:%22wallaby-no-change-libs%22+(status:open%20OR%20status:merged)))12:36
hberaudand https://review.opendev.org/q/topic:%22wallaby-cycle-highlights%22+(status:open%20OR%20status:merged)12:36
hberaudI'll generate them12:36
ttxthanks!12:37
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.limit for wallaby  https://review.opendev.org/c/openstack/releases/+/77999312:39
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.middleware for wallaby  https://review.opendev.org/c/openstack/releases/+/77999412:42
openstackgerritHervé Beraud proposed openstack/releases master: Release oslo.privsep for wallaby  https://review.opendev.org/c/openstack/releases/+/77999512:45
hberaudWell, I think we're pretty good here.12:45
openstackgerritMerged openstack/releases master: Add Neutron Wallaby highlights  https://review.opendev.org/c/openstack/releases/+/77948712:56
*** openstack has joined #openstack-release13:16
*** ChanServ sets mode: +o openstack13:16
openstackgerritHervé Beraud proposed openstack/releases master: Release final python-ironicclient for Wallaby  https://review.opendev.org/c/openstack/releases/+/77896213:18
openstackgerritMerged openstack/releases master: Create ovb 2.0 release and cut stable/2.0 branch  https://review.opendev.org/c/openstack/releases/+/77928213:23
*** nweinber has joined #openstack-release13:45
openstackgerritDaniel Bengtsson proposed openstack/releases master: New bugfix release of oslo.messaging.  https://review.opendev.org/c/openstack/releases/+/78001014:18
yoctozeptohberaud: thanks, will check it out then15:00
openstackgerritHervé Beraud proposed openstack/releases master: [FFE] OpenstackSDK 0.55.0  https://review.opendev.org/c/openstack/releases/+/78001315:10
hberaudyoctozepto: the OpenstackSDK part ^15:12
yoctozeptohberaud: thanks, I have just finished reading mails :-)15:12
hberaud:)15:13
yoctozeptohad a long meetings streak15:13
openstackgerritHervé Beraud proposed openstack/releases master: [FFE] OpenstackSDK 0.55.0  https://review.opendev.org/c/openstack/releases/+/78001315:19
*** dirk2 is now known as dirk15:23
*** nweinber has quit IRC15:48
hberauddtantsur: o/ I updated to a bugfix version => https://review.opendev.org/c/openstack/releases/+/778962 let us know if that works for you15:57
dtantsurthank you, I have it on the radar, just trying to finish something here15:57
hberaudnp thanks15:57
gmannhberaud: ttx can you add wallaby release status for Zaqar in this etherpad https://etherpad.opendev.org/p/xena-leaderless16:01
gmannit is leader-less project in Xena16:01
clarkbhberaud: the major reason for it is to ensure that a recent change that handles how git state is handled for a buildset is verified outside of the test suite16:02
hberaudgmann: I'm not sure to see the link between release management and leader less project?16:02
clarkbhberaud: maybe we still plan for friday as things tend to slow down by then? and if it has an impact we can extend?16:02
gmannhberaud: i mean TC can judge if no release happening then it is time for retirement or so16:02
hberaudAh got it16:03
gmannrelease status is one of  the input for TC16:03
hberaudYou speak about other projects16:03
hberauds/projects/teams/16:03
gmannoh , sorry its Zaqar  only16:03
yoctozeptogmann, hberaud: fwiw, I "confirmed" it stalled with releases16:04
yoctozeptobut hberaud is welcome to confirm better than I can :D16:04
*** armstrong has joined #openstack-release16:07
hberaudgmann, yoctozepto: I commented all the given projects16:24
gmannhberaud: thanks a lot, it is helpful16:25
hberaudgmann: you're welcome :)16:25
yoctozeptohberaud: yes, thanks!16:26
hberaudclarkb: I think we can wait until early next week (monday).16:26
hberaudyoctozepto: you're welcome )16:26
*** nweinber has joined #openstack-release16:31
*** prometheanfire has joined #openstack-release16:34
openstackgerritMarios Andreou proposed openstack/releases master: Tag master/victoria/ussuri release for os-collect-config  https://review.opendev.org/c/openstack/releases/+/78003416:35
prometheanfirehow is releases doing for the freeze?  think reqs should expect stragglers?16:39
hberaudprometheanfire: for now things are doing well, I think we will have few stragglers16:42
hberaudprometheanfire: At least those with -1 https://review.opendev.org/q/topic:%22wallaby-no-change-libs%22+(status:open%20OR%20status:merged)16:43
hberaudhttps://review.opendev.org/q/topic:%2522cwi-client-final%2522+(status:open)16:43
hberaudgibi, bauzas: o/ Please can you've a look? https://review.opendev.org/c/openstack/releases/+/77897716:45
gibihberaud: I'm on it16:46
prometheanfirecool, thanks16:46
hberaudthanks16:46
prometheanfirethat's actually not TOOO bad16:46
hberaudYeah I think we'll have a better picture tomorrow morning16:47
hberaud#startmeeting releaseteam17:00
openstackMeeting started Thu Mar 11 17:00:13 2021 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
hberaud#link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda17:00
*** openstack changes topic to " (Meeting topic: releaseteam)"17:00
openstackThe meeting name has been set to 'releaseteam'17:00
hberaudPing list: ttx armstrong elod damani17:00
elodo/17:00
armstrongo/17:00
hberaudWe're way down on line 411 now.17:01
hberaudWill just wait a couple minutes for folks.17:01
armstrongok17:01
hberaud#topic Review task completion17:04
*** openstack changes topic to "Review task completion (Meeting topic: releaseteam)"17:04
hberaudProcess any remaining library freeze exception => Done17:04
hberaudEarly in the week, email openstack-discuss list to remind PTLs that cycle-highlights are due this week => Done17:04
hberaudPropose autoreleases for cycle-with-intermediary client libraries which had commits that have not been included in a release => Patches need validations17:04
hberaudhttps://review.opendev.org/q/topic:%2522cwi-client-final%2522+(status:open)17:04
hberaudhttps://review.opendev.org/q/topic:%22wallaby-no-change-libs%22+(status:open)17:04
hberaudelod, ttx: feel free to validate those accepted by PTLs and that needs a final +2 ^17:06
ttxo/17:06
hberaudo/17:06
elodhberaud: ack17:06
hberaudconcerning those we missed ( https://review.opendev.org/q/topic:%22wallaby-no-change-libs%22+(status:open) ) do we want to wait for PTLs/liaisons?17:07
hberaudSince no significant changes have been merged yet maybe we could simply force them17:07
hberaudAny opinion?17:07
ttxI'd wait until Monday yes17:08
hberaudelod: it would be nice to merge those who have been approved today17:08
hberaudttx: it's okay with me17:09
armstrong@ttx +117:09
hberaudprometheanfire: FYI ^17:09
elodhberaud: ack, too :)17:09
hberaudwe will wait until monday for a couple of patches17:09
hberaudprometheanfire: I think that if requirements updates aren't in these lists who should refuse them17:10
hberauds/who/we17:11
*** fnordahl has joined #openstack-release17:11
hberaudok next task from last week17:11
hberaudEvaluate any libraries that did not have any change merged over the cycle => partially done, @ttx: do you want to add something?17:12
hberaudhttps://review.opendev.org/q/topic:%22move-to-independent%22+(status:open)17:12
ttxno that's under control I think17:12
hberaudI think we can approve the oslo part17:13
hberaudany volunteer to push the final button?17:13
hberaudOk I'll approve oslo17:14
hberaudI don't expect that the oslo part will receive new comments as it have been already discussed previously this cycle17:15
hberaudOk next task from last week17:17
hberaudList cycle-with-intermediary deliverables that have not been released yet => Done thanks armstrong17:17
armstrongnp17:17
hberaudhttp://lists.openstack.org/pipermail/openstack-discuss/2021-March/020989.html17:17
hberaudAFAIK we didn't get any feedback apart from requirements team17:18
*** diablo_rojo has joined #openstack-release17:20
* diablo_rojo joins late17:20
hberaudo/17:20
prometheanfireack17:21
hberaudnext task was "On Friday, remind the requirements team to freeze changes to openstack/requirements" => already started17:21
hberaudthat point depends on the previous ones17:21
hberaudok next topic17:22
hberaud#topic Assign R-4 tasks17:22
*** openstack changes topic to "Assign R-4 tasks (Meeting topic: releaseteam)"17:22
hberaudthanks armstrong for taking this on17:22
hberaudone17:22
hberaudwell, everything seems more or less already distribued17:22
hberaudarmstrong: yours is more or less similar to your previous one17:23
armstrongok17:23
hberaudAnything else to add for next week tasks?17:24
hberaudOk move on17:25
hberaud#topic Review countdown email contents17:25
*** openstack changes topic to "Review countdown email contents (Meeting topic: releaseteam)"17:25
hberaud#link https://etherpad.opendev.org/p/relmgmt-weekly-emails17:25
diablo_rojoLooks all correct to me.17:28
hberaud\o/17:28
diablo_rojoI am only one set of eyes though :)17:28
diablo_rojoHopefully others can check it too.17:28
hberaudrotfl17:28
ttx+117:29
diablo_rojoI guess, as a one off we could add one final call for cycle highlights17:29
diablo_rojobut I can do that in a separate email17:29
diablo_rojoin hopes that more people actually see it lol17:29
hberaudCan't hurt17:30
diablo_rojoso, coming full circle, lol, it looks good to me.17:30
hberaudok thanks17:30
armstrongLGTM17:30
diablo_rojoThank you hberaud :) And congrats on being our fearless leader for another cycle.17:30
hberaudMy pleasure! This is a fearless team so it's not complicated for me17:31
hberaudOk move on17:31
hberaud#topic Releasing requirements - Tagless project17:31
*** openstack changes topic to "Releasing requirements - Tagless project (Meeting topic: releaseteam)"17:31
hberaud#link https://review.opendev.org/c/openstack/releases/+/77983217:32
hberaudJust a minor heads up about this patch17:32
hberaudAs said in my latest comment I think we need to hold this one until our batches of patches are fully merged.17:33
hberaudAny opinion?17:33
ttxI'm wondering why we need to release this17:33
ttxdigging in17:33
hberaudAlso reqs is tagless so I don't think we need a version17:34
hberaudI think we only need to cut the branch that's all17:34
ttxright17:34
ttxyou just need a location17:34
hberaudAlready discussed about this with prometheanfire (FYI ^)17:34
fungiyes, requirements branches but it doesn't release17:34
ttxok17:35
ttxhttps://opendev.org/openstack/releases/src/branch/master/deliverables/victoria/requirements.yaml17:35
hberaudThanks for your confirmation17:35
prometheanfireya, once we freeze and get those last client releases into reqs we can branch17:35
ttxthen yes it should match req freeze17:35
hberaudyeah and ussuri did the same17:35
hberaudthanks prometheanfire17:35
ttxlast time we waited until Oct 417:36
ttxthat's R-217:36
openstackgerritMichael Johnson proposed openstack/releases master: Release Octavia 6.2.0 for stable/ussuri  https://review.opendev.org/c/openstack/releases/+/77950317:36
hberaudyeah final RC17:36
hberaudthat's not too late?17:37
prometheanfirethere are some projects that are used as libs (horizon and neutron mainly), not sure if we need to wait for something there17:37
ttxIt's in the process17:37
hberaudhowever it's just one more weeks17:37
hberaudok sold17:38
ttxPretty sure we should wait until R-2 to make sure we have all the exceptions in17:38
hberaudSold17:38
ttxeven if in theory it should not move17:38
hberaudmake sense17:38
hberaudprometheanfire: WFY?17:38
prometheanfireWFY?17:40
hberaudthat works for you? (freezing on R-2)17:40
prometheanfireyes17:41
hberaudI just left a related comment directly on the patch17:41
fungithe way zuul jobs integrate branches of required projects, if no matching branch name exists master is used, so that means projects should be able to branch ahead of requirements17:41
hberaudok cool17:41
fungibut requirements will still have to remain frozen until it branches17:41
hberaudI see17:42
hberaudthanks for details17:42
prometheanfireyep, last time it was just a couple of weeks, 1-2, I'm trying to reduce the time17:42
hberaudMaybe we could discuss this point on PTG?17:43
hberaud(reducing the time)17:43
hberaudOK, we can discuss this point after the meeting.17:44
hberaud#topic Governance oversight - Freshly added projects not present in release17:44
prometheanfireya17:44
*** openstack changes topic to "Governance oversight - Freshly added projects not present in release (Meeting topic: releaseteam)"17:44
ttxmust be very fresh17:45
hberaudI made another round of vigilance17:45
ttxwerent around at m-2 for sure17:45
hberaudok so I think we should ignore them17:45
ttxwhich is theoretically when we freeze (so that we do not have to do a last round of vigilance :) )17:45
hberaudI prefered to ask first17:45
hberaudok :)17:46
hberaudnext topic17:46
hberaud#topic Tag and create missing ussuri branch os-refresh-config17:46
*** openstack changes topic to "Tag and create missing ussuri branch os-refresh-config (Meeting topic: releaseteam)"17:46
hberaudttx and myself agreed about https://review.opendev.org/c/openstack/releases/+/77663617:47
hberaudhowever I wanted to give a chance to react before pushing the buttons17:47
ttxyeah I don;t care enough about the issue to spend more time on it17:47
hberaudelod: FYI ^17:48
ttxboth work17:48
ttx(not doing it and doing it) so let's not spend too much time on it17:48
hberaudOk then I just +2'd17:48
elodhberaud: I don't have hard feelings either, looks OK :)17:48
hberaudok thanks17:48
hberaudfeel free to close the debate17:49
hberaud#topic OpenstackSDK transition to client-library?17:49
*** openstack changes topic to "OpenstackSDK transition to client-library? (Meeting topic: releaseteam)"17:49
hberaudso yoctozepto asked for a FFE on openstackSDK17:49
hberaudhttp://lists.openstack.org/pipermail/openstack-discuss/2021-March/021004.html17:49
hberaudeverybody approved17:50
ttxI think this is not urgent. That affects where the library appears on release page. And when the deadline is17:50
ttx(the transition to client-lib)17:50
hberaudok17:50
ttxSo we can keep that thread open and push the patch if needed17:50
ttxthe urgent thing is the FFE17:50
hberaudI see, that's point is done17:51
hberaudOk move on17:51
hberaud#topic Feature branch for Helm17:51
*** openstack changes topic to "Feature branch for Helm (Meeting topic: releaseteam)"17:51
ttxPersonally I would keep it the same and consider moving it for next cycle17:51
hberaud#link https://review.opendev.org/c/openstack/releases/+/77958317:52
hberaud+117:52
ttxSo this one... basically helm is not using release management but wants a feature branch created17:52
hberaudyes17:52
ttxI don;t think they should create a deliverable file for that17:52
ttxWe can create the branch manually17:52
hberaudAFAIK normally they have credential to create branches17:53
hberaudno?17:53
ttxchecking17:53
hberaudI think it's depends on if they are a SIG or not17:53
hberaudI'm not sure on this point17:54
ttxhmm newest gerrit does not display ACLs anymore17:54
hberaudfungi: any idea? ^17:55
ttxchecking config files17:55
fungithey've already worked that out with the tact sig/opendev17:55
ttxah then just abandon17:55
fungiwe merged a change yesterday or today to allow them to create branches manually themselves17:55
ttxhttps://review.opendev.org/admin/repos/openstack/openstack-helm,access is a bit dry17:55
hberaudok so let's just abandon the patch17:56
ttxfungi: if you have a ref we can close https://review.opendev.org/c/openstack/releases/+/779583    referencing it17:56
fungigerrit hides acl entries from you if you're not authorized to do those things described by the acl17:56
ttxfungi: even on repos I have large rights on it looks very dry. But off topic17:56
hberaudah I missed that it was already abandonned17:56
ttxah ENOTAPROBLEM -- next topic!17:57
hberaudOk next topic17:57
fungi#link https://review.opendev.org/779872 Add create ref acl for osh release groups17:57
hberaud#topic Release errors17:57
*** openstack changes topic to "Release errors (Meeting topic: releaseteam)"17:57
hberaudTripleo-ipsec tagging issue17:57
ttxI have not caught up on that thread17:57
ttxchecking now17:58
fungithat's the one where it looks like their .gitreview file may not have ever been updated to the new review.opendev.org hostname, and we may not be preinstalling a known_hosts entry for the old name17:58
fungispecifically on the stable/rocky branch they'17:58
fungire trying to eol17:58
ttxok let's do (2) as suggested17:59
hberaud+117:59
ttxnext!17:59
elod+117:59
ttxwe can still make it17:59
hberaud    yarn fail http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021002.html17:59
elod:D17:59
ttx15 seconds left17:59
hberaudI think we need a js expert here17:59
ttxwtf yarn!18:00
hberaudsurely a package manager18:00
ttxyeah it's athe NPM upload thing iirc18:00
ttxlet's wait for someone to chime in18:00
hberaudI propose to continue this topic directly on the ML18:00
fungidoes that job fail consistently for all projects using it, or only that repo?18:00
hberaudI'll add a note for next weel18:01
hberaudweek18:01
fungibut yeah, ml makes more sense18:01
hberaudok next point18:01
hberaud#topic PTG reminder18:01
*** openstack changes topic to "PTG reminder (Meeting topic: releaseteam)"18:01
hberaudDon't forget to vote18:01
ttxfungi:  last time it worked was in 201718:01
ttxlast time it ran was in 2017 too.18:02
fungiwow18:02
hberaud#link https://doodle.com/poll/8d8n2picqnhchhsv18:02
ttxhttps://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-javascript&project=openstack/monasca-grafana-datasource18:02
ttxah hm18:02
ttxtoo many filters18:02
hberaud#link https://etherpad.opendev.org/p/xena-ptg-os-relmgt18:02
hberaudFeel free to add topics to our etherpad18:02
ttxit actually ran successfully last time, but that was 18months ago18:03
fungi2019-09-26 yeah18:03
hberaud#topic Quick Open Discussion18:03
*** openstack changes topic to "Quick Open Discussion (Meeting topic: releaseteam)"18:03
ttxIt's independent so not really release-process-critical18:03
openstackgerritMerged openstack/releases master: Tag and create missing ussuri branch os-refresh-config  https://review.opendev.org/c/openstack/releases/+/77663618:03
ttxhberaud: thanks!18:03
hberaudAnything else?18:03
hberaudSorry we overflowed a little18:04
ttxnp18:04
ttxit's feature freeze after all18:04
hberaud:)18:04
ttxIf we do not overflow today, when do we18:04
hberaudchampagne18:04
hberaud+20 minutes18:04
hberaud(free)18:05
ttxhttps://stackoverflow.com/questions/64414716/unexpected-token-in-yarn-installation18:05
ttx"The error is caused by the old version of nodejs (usually lower than v6)."18:05
ttxyay backward compatibility18:06
hberaudhttps://governance.openstack.org/tc/reference/runtimes/wallaby.html#node-js-runtime-for-wallaby18:06
hberaudWe use nodejs 1018:06
ttxnot sure that's what is installed on the host tho18:07
hberaudhm wait which branch it was?18:07
ttxindependent so master18:07
hberaudok18:08
hberaudSo I suppose it rely on the series supported runtimes18:08
ttxI bet system-installed yarn is older than nodejs1018:08
hberaudcould be18:09
ttxbut then I'm just speaking weird words18:09
ttxyarn node node yarn18:09
hberaud:)18:09
ttxSo let's wait for ML discussion with people who actually grok js18:09
hberaud+118:09
hberaudAnything else?18:09
ttxmaybe push it back to next week meet agenda so that it does not fall between the cracks18:10
hberaudalready done18:10
ttxmy man!18:10
hberaudlol18:10
*** eolivare has quit IRC18:10
hberaudOK, thanks everyone. Let's wrap up!18:11
hberaud#endmeeting18:11
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/"18:11
openstackMeeting ended Thu Mar 11 18:11:20 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-03-11-17.00.html18:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-03-11-17.00.txt18:11
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-03-11-17.00.log.html18:11
elodthanks o/18:11
yoctozeptoqq - horizon plugins count as libraries / client libraries?18:31
hberaudyoctozepto: horizon plugins count as horizon plugins :) https://releases.openstack.org/reference/deliverable_types.html#horizon-plugin https://releases.openstack.org/reference/process.html#r-4-week18:34
hberaudyoctozepto: deadline for this kind of deliverable is next week ^18:34
yoctozeptohberaud: lovely, thanks18:35
*** dtantsur is now known as dtantsur|afk18:39
*** nweinber has quit IRC18:49
openstackgerritMerged openstack/releases master: Release final python-novaclient for Wallaby  https://review.opendev.org/c/openstack/releases/+/77897719:34
*** e0ne has joined #openstack-release19:45
openstackgerritMerged openstack/releases master: Release final python-tackerclient for Wallaby  https://review.opendev.org/c/openstack/releases/+/77897219:45
openstackgerritMerged openstack/releases master: Release python-zunclient for wallaby  https://review.opendev.org/c/openstack/releases/+/77997819:52
openstackgerritIvan Kolodyazhny proposed openstack/releases master: Release horizon v19.1.0 (wallaby-3)  https://review.opendev.org/c/openstack/releases/+/78009919:58
openstackgerritMerged openstack/releases master: Release oslo.privsep for wallaby  https://review.opendev.org/c/openstack/releases/+/77999520:15
openstackgerritMerged openstack/releases master: Release oslo.limit for wallaby  https://review.opendev.org/c/openstack/releases/+/77999320:20
openstackgerritMerged openstack/releases master: Release oslo.middleware for wallaby  https://review.opendev.org/c/openstack/releases/+/77999420:28
*** e0ne has quit IRC20:36
*** armstrong has quit IRC20:37
*** nweinber has joined #openstack-release20:38
*** slaweq has quit IRC20:56
*** e0ne has joined #openstack-release21:06
*** nweinber has quit IRC21:11
openstackgerritRadosław Piliszek proposed openstack/releases master: Release final python-masakariclient for Wallaby  https://review.opendev.org/c/openstack/releases/+/78011521:27
*** jbadiapa has quit IRC22:40
*** smcginnis has quit IRC23:04
*** smcginnis has joined #openstack-release23:15
*** e0ne has quit IRC23:16
*** diablo_rojo has quit IRC23:16
*** smcginnis has quit IRC23:28
*** diablo_rojo has joined #openstack-release23:32

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